Coordinated leaving for concurrent RRC procedures in a multiple-SIM UE

ABSTRACT

Coordinated leaving for a UE having a first SIM and a second SIM may include decoding, at a baseband processor, an RRC reconfiguration message associated with the first SIM received from a first network. A communication corresponding to the second SIM received from a second network is decoded while the baseband processor is processing the received RRC reconfiguration message. The communication received from the second network is determined to comprise a higher priority than the RRC reconfiguration procedure. Based on determining, a UAI message corresponding to the first SIM is encoded by the baseband processor for transmission to the first network. The UAI message is configured to inform the first network of coordinated leaving and abortion of the RRC reconfiguration procedure. The first SIM is transitioned to an idle mode. An RRC request corresponding to the second SIM is encoded by the baseband processor for transmission to the second network.

TECHNICAL FIELD

This application relates generally to wireless communication systems, including the handling of coordinated leaving procedures multiple universal subscriber identify module (MUSIM) user equipments (UEs).

BACKGROUND

Wireless mobile communication technology uses various standards and protocols to transmit data between a base station and a wireless mobile device. Wireless communication system standards and protocols can include the 3rd Generation Partnership Project (3GPP) long term evolution (LTE) (e.g., 4G) or new radio (NR) (e.g., 5G); the Institute of Electrical and Electronics Engineers (IEEE) 802.16 standard, which is commonly known to industry groups as worldwide interoperability for microwave access (WiMAX); and the IEEE 802.11 standard for wireless local area networks (WLAN), which is commonly known to industry groups as Wi-Fi. In 3GPP radio access networks (RANs) in LTE systems, the base station can include a RAN Node such as a Evolved. Universal Terrestrial Radio Access Network (E-UTRAN) Node B (also commonly denoted as evolved Node B, enhanced Node B, eNodeB, or eNB) and/or Radio Network Controller (RNC) in an E-UTRAN, which communicate with a wireless communication device, known as user equipment (UE). In fifth generation (5G) wireless RANs, RAN Nodes can include a 5G Node, NR node (also referred to as a next generation Node B or g Node B (gNB)).

RANs use a radio access technology (RAT) to communicate between the RAN Node and UE. RANs can include global system for mobile communications (GSM), enhanced data rates for GSM evolution (EDGE) RAN (GERAN), Universal Terrestrial Radio Access Network (UTRAN), and/or E-UTRAN, which provide access to communication services through a core network. Each of the RANs operates according to a specific 3GPP RAT. For example, the GERAN implements GSM and/or EDGE RAT, the UTRAN implements universal mobile telecommunication system (UMTS) RAT or other 3GPP RAT, the E-UTRAN implements LTE RAT, and NG-RAN implements 5G RAT. In certain deployments, the E-UTRAN may also implement 5G RAT.

Frequency bands for 5G NR may be separated into two different frequency ranges. Frequency Range 1 (FR1) includes sub-6 GHz frequency bands, some of which are bands that may be used by previous standards, but may potentially be extended to cover potential new spectrum offerings from 410 MHz to 7125 MHz. Frequency Range 2 (FR2) includes frequency bands from 24.25 GHz to 52.6 GHz. Bands in the millimeter wave (mmWave) range of FR2 have shorter range but higher available bandwidth than bands in the FR1. Skilled persons will recognize these frequency ranges, which are provided by way of example, may change from time to time or from region to region.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

To easily identify the discussion of any particular element or act, the most significant digit or digits in a reference number refer to the figure number in which that element is first introduced.

FIG. 1 illustrates an example data flowchart between multiple SIMs of a multi-SIM device and multiple networks.

FIG. 2 illustrates an example data flowchart between multiple SIMs of a multi-SIM device and multiple networks.

FIG. 3 illustrates an example data flowchart between multiple SIMs of a multi-SIM device and multiple networks.

FIG. 4 illustrates an example data flowchart between multiple SIMs of a multi-SIM device and multiple networks.

FIG. 5 illustrates an example data flowchart between multiple SIMs of a multi-SIM device and multiple networks.

FIG. 6 illustrates an example data flowchart between multiple SIMs of a multi-SIM device and multiple networks.

FIG. 7 illustrates an example data flowchart between multiple SIMs of a multi-SIM device and multiple networks.

FIG. 8 illustrates a flowchart of a method for a coordinated leaving procedure of a multi-SIM UE.

FIG. 9 illustrates a flowchart of a method for a coordinated leaving procedure of a multi-SIM UE.

FIG. 10 illustrates a flowchart of a method for a coordinated leaving procedure of a multi-SIM UE.

FIG. 11 illustrates a system in accordance with one embodiment.

FIG. 12 illustrates an infrastructure equipment in accordance with one embodiment.

FIG. 13 illustrates a platform in accordance with one embodiment.

FIG. 14 illustrates a device in accordance with one embodiment.

FIG. 15 illustrates example interfaces in accordance with one embodiment.

FIG. 16 illustrates components in accordance with one embodiment.

DETAILED DESCRIPTION

Coordinated leaving, as further described in 3GPP TR 23.761, Section 6.5, currently includes a number of issues to be resolved with respect to the use of multiple universal subscriber identity modules (USIMs) on a single UE (e.g., a mobile phone). By way of background, coordinated leaving is an issue associated with Multi-USIM (MUSIM) devices that have concurrent registrations associated with at least two USIMs. For instance, while actively communicating with a first network associated with a first USIM of a MUSIM device, the MUSIM device may determine that some activity (e.g., responding to a page) of a second network associated with a second USIM of the MUSIM device is to be performed. Accordingly, coordinated leaving may be particularly applicable to MUSIM devices that lack capability to concurrently connect to multiple networks with multiple SIMS of such MUSIM devices.

Currently, no procedure exists for notifying a network that a SIM of a MUSIM device may autonomously leave or release a radio resource control (RRC) connection with the network (i.e., via the baseband processor). Such actions may be interpreted as an error case and have the potential to distort statistics and/or misguide other procedures. In addition, during the SIM's absence, the UE may not receive downlink data or process paging, which may result in a waste of resources.

FIG. 1 illustrates a data flowchart between multiple SIMs of a MUSIM device (not shown) and multiple networks (NWs) that includes coordinated leaving signaling, as further described herein. As shown, FIG. 1 includes two SIMs of a MUSIM device, SIM A 102 and SIM B 104, and two associated NWs, NW A 106 and NW B 108. In an example, as part of the coordinated leaving described in 3GPP TR 23.761 (section 6.5), a MUSIM UE may trigger coordinated leaving on SIM A 102 in connected mode (i.e., with NW A 106) in order to process Mobile Terminated (MT) Paging on SIM B 104 (or any other high priority Mobile-originated (MO) activity on SIM B 104.

In particular, arrow 110 from NW A 106 to SIM A 102 may represent an RRC reconfiguration procedure. During such reconfiguration, a paging request may be sent from the NW B 108 to the SIM B 104 (i.e., via the baseband processor), as represented by arrow 112. In response to such paging request, the baseband processor of the LTE may send coordinated leaving signaling associated with SIM A 102 to NW A 106, as represented by arrow 114. NW A 106 may then perform an RRC release procedure to place the SIM A 102 in an idle/inactive state (as represented by arrow 116). The baseband processor may then send an RRC request corresponding to SIM B and the paging request to NW B 108 (as represented by arrow 118).

Notably, coordinated leaving may be performed at the non-access stratum (NAS) layer or the access stratum (AS) layer. When coordinated leaving is executed at the AS layer, the scenario shown in FIG. 1 is possible. In particular, SIM A 102 is in RRC Connected mode and receives RRC reconfiguration message (i.e., via the baseband processor) from the network and the baseband processor processes the RRC reconfiguration. While the baseband processor is processing the RRC reconfiguration message corresponding to SIM A, SIM B 104 (which may be in idle mode) may get paged (or another high priority activity that includes an RRC connection may be triggered).

With respect to coordinated leaving, the disclosure herein discusses various procedural possibilities that may be utilized and any corresponding issues to be defined. For instance, 1. SIM A 102 (via the baseband processor) completes the RRC reconfiguration by sending an RRC reconfiguration Complete message to the NW A 106 followed by performing the coordinated leaving procedure; or 2. The RRC reconfiguration procedure is abandoned and the baseband processor sends a coordinated leaving message corresponding to SIM A to the NW A 106 immediately. A similar situation may exist irrespective of the layer at which coordinated leaving occurs (i.e., the AS layer or the NAS layer).

A first detailed solution may include aborting a received RRC reconfiguration and triggering coordinated leaving, as further described with respect to FIG. 2 . In particular, upon reception of (high priority) paging associated with SIM B 204 (or an activity that is higher priority than the activity on SIM A 202 is triggered on SIM B 204), the baseband processor can the trigger coordinated leaving procedure associated with SIM A 202 before completing the ongoing RRC reconfiguration. This solution may be particularly applicable when the baseband processor hasn't applied (or started processing) the new configuration associated with SIM A 202 received in the corresponding RRC reconfiguration and SIM B 204 (via the baseband processor) has to establish an RRC Connection. For instance, the first detailed solution (i.e., aborting reconfiguration) may be suitable for a scenario in which SIM A 202 (via the baseband processor) has received an RRC reconfiguration that includes conditional configuration (e.g., a conditional handover since the actual handover is a future event). The UE (and ultimately, the baseband processor of the UE) can then abort the RRC reconfiguration of SIM A 202 to perform RRC Connection with respect to SIM B 204.

More specifically, as illustrated by FIG. 2 . SIM A 202 may initially be in a connected state (as represented by block 210) with respect to NW A 206 while SIM B 204 may be in an inactive/idle state (as represented by block 212). Once again, the baseband processor may be performing an RRC reconfiguration procedure associated with SIM A 202 when paging from NW B 208 to SIM B 204 occurs, as represented by arrow 214 and arrow 216, respectively.

SIM B 204 may then send a suspend request to SIM A 202 in response to receiving the paging request, as represented by arrow 218 (which communications may occur via the baseband processor). The baseband processor may then consider the ongoing RRC reconfiguration procedure of SIM A 202 as failed and send a OF Assistance Information (UAI) to NW A 206 with a new cause FailureInfoRRCMUSIM-r17-CoordinatedLeaving, as represented by arrow 220. Using the RRC configuration that was configured prior to receiving the RRC reconfiguration message (i.e., represented by arrow 214) and upon receiving the RRC Release from NW A 206 (i.e., represented by arrow 222), the MUSIM having SIM A 202 and SIM B 204 exits connected mode with respect to SIM A 202 (i.e., as represented by arrow 222, block 224, and arrow 226) and starts connection establishment on SIM B 204, as represented by arrow 228.

A second detailed solution may include complete RRC reconfiguration and triggering coordinated leaving, as further described with respect to FIG. 3 through FIG. 6 . Accordingly, four different options associated with the second detailed solution may be utilized, a first option detailed with respect to FIG. 3 , a second option detailed with respect to FIG. 4 , a third option detailed with respect to FIG. 5 , and a fourth option detailed with respect to FIG. 6 . As illustrated in FIG. 3 , in the first option of the second detailed solution, SIM A 302 may initially be in a connected state (as represented by block 310) with respect to NW A 306 while SIM B 304 may be in an inactive/idle state (as represented by block 312. Once again, the baseband processor may be processing a received RRC reconfiguration associated with SIM A 302 when paging from NW B 308 to SIM B 304 occurs, as represented by arrow 314 and arrow 316, respectively.

In response to the paging received by SIM B 304 (via the baseband processor), SIM B 304 may send a suspend request to SIM A 302, as represented by arrow 318 (which actions may ultimately be handled by the baseband processor). The baseband processor may then complete the ongoing RRC reconfiguration corresponding to SIM A 302 (i.e., the RRC reconfiguration corresponding to arrow 314) and trigger the coordinated leaving procedure by piggybacking a coordinated leaving message over the RRC reconfiguration Complete message, as represented by arrow 320. NW A 306 may then process the RRC reconfiguration Complete message and the piggybacked coordinated leaving message to trigger coordinated leaving. NW A 306 may then send an RRC Release to SIM A 302 (via the based band processor), as represented by arrow 322. SIM A 302 may then be transitioned into idle mode, as represented by block 324 and arrow 326. The baseband processor starts connection establishment for SIM B 304 by sending an RRC Request, as represented by arrow 328.

As illustrated in FIG. 4 , in the second option of the second detailed solution, SIM A 402 may initially be in a connected state (as represented by block 410) with respect to NW A 406 while SIM B 404 may be in an inactive/idle state (as represented by block 412). Once again, the baseband processor may be processing a received RRC reconfiguration associated with SIM A 402 when paging from NW B 408 to SIM B 404 occurs, as represented by arrow 414 and arrow 416, respectively.

In response to the paging associated with SIM B 404 being received, SIM B 404 may send a suspend request to SIM A 402, as represented by arrow 418 (which actions are ultimately performed by the baseband processor). The baseband processor may then complete the RRC reconfiguration associated with SIM A 402 and signal coordinated leaving to the NW by sending a UAI message with new cause, as represented by arrow 420. NW A 406 may be configured to accept and process the UAI (with new cause) from the UE/SIM A 402 instead of the RRC reconfiguration Complete message (e.g., as is the case with respect to FIG. 3 ). NW A 406 may then send an RRC Release to SIM A 402 (via the baseband processor), as represented by arrow 422. SIM A 402 may then be transitioned into idle mode, as represented by block 424 and arrow 426. The baseband processor starts connection establishment by sending an RRC Request associated with SIM B 404, as represented by arrow 428.

As illustrated in FIG. 5 , in the third option of the second detailed solution, SIM A 502 may initially be in a connected state (as represented by block 510) with respect to NW A 506 while SIM B 504 may be in an inactive/idle state (as represented by block 512). Once again, the baseband processor may be processing a received RRC reconfiguration associated with SIM A 502 when paging from NW B 508 to SIM B 504 (i.e., via the baseband processor) occurs, as represented by arrow 514 and arrow 516, respectively.

In response to the paging received by SIM B 504 (via the baseband processor), the baseband processor may send a BUSY indication associated with SIM B 504 to NW B 508 (as represented by arrow 518; with optional retry T_RETRY represented by arrow 538, which comprises the remaining time by which the baseband processor has to send the response in UL for RRC signaling associated with SIM A 502) to indicate that a current time constraint associated with RRC signaling being handled in association with the other SIM (i.e., SIM A 502). Upon sending the RRC reconfiguration Complete associated with SIM A 502 (as represented by arrow 520), the baseband processor may handle the previous page associated with SIM B 504 and trigger a suspend to SIM A 502 (as represented by arrow 524). The baseband processor may then send coordinated leaving signaling associated with SIM A 502 to NW A 506, as represented by arrow 526. After RRC Release associated with SIM A 502 (as represented by arrow 528). SIM A 502 may be transitioned to idle mode, as represented by block 530 and arrow 532, and the baseband processor may process the normal page handling associated with SIM B 504 (as represented by arrow 534).

In such an approach, the BUSY indication to NW B 508 itself can act as an implicit acknowledgement from NW B 508 that it has received the page and that the NW B 508 can respond back within a time period, T_RETRY (e.g., 10 milliseconds (ms)). In addition, the following possibilities may be applicable to this solution: 1. The baseband processor may send coordinated leaving signaling associated with SIM A 502 piggybacked with an RRC reconfiguration Complete message; 2. When NW B 508 processes the BUSY indication, it may start the T_RETRY timer. Upon expiration of the timer, NW B 508 may retry paging SIM B 504 (i.e., via the baseband processor). The UE/SIM B 504 (and ultimately the baseband processor of the UE) may process the high priority signaling (e.g., the paging) and proceed further. In such case, no paging buffering is needed in association with SIM B 504; and 3. The BUSY indication can be sent via an existing random access channel (RACH) procedure or using a dedicated, pre-defined idle/inactive configuration.

Notably, options one through three of the second detailed solution may be particularly suitable for situations in which an RRC reconfiguration contains “mobilityInfo” (i.e., handover information) for handover and the UE informs the target cell of coordinated leaving rather than the source cell (which source cell may be weak and miss the UE's UL messages). In particular, these options may be suitable for such situations because they complete the RRC configuration and send a coordinated leaving message to the target cell (i.e. the new cell for which the NW A asks the UE to perform a handover). Similarly, options one through three may be suitable for scenarios in which SIM B 504 is paged (via the baseband processor) while the baseband processor is performing a conditional handover associated with SIM A 502 (i.e. handing over to a candidate cell configured earlier in a reconfiguration message with conditional configuration).

As illustrated in FIG. 6 , in the fourth option of the second detailed solution, SIM A 602 may initially be in a connected state (as represented by block 610) with respect to NW A 606 while SIM B 604 may be in an inactive/idle state (as represented by block 612). Once again, the baseband processor may be processing an RRC reconfiguration associated with SIM A 602 when paging from NW B 608 to SIM B 604 (i.e., via the baseband processor) occurs, as represented by arrow 614 and arrow 616, respectively.

In response to the paging received that corresponds to SIM B 604, SIM B 604 may send a suspend request to SIM A 602 (which actions may be ultimately handled by the baseband processor) due to a high priority activity (e.g., receiving a paging message) while the baseband processor is processing the RRC reconfiguration associated with SIM A 602, as represented by arrow 618. The baseband processor may apply a limited number of configurations (defined by 3GPP) corresponding to SIM A 602. For instance, in some embodiments, such configurations may include mandatory primary cell (Pcell) configurations received in a reconfiguration message that can impact the UE's radio link quality or access to the NW. In such embodiments, whether or not RRC reconfiguration includes mobility info (for handover) may be ignored. Accordingly, when no Pcell configuration is received, the baseband processor will not apply any configurations to SIM A 602 in such embodiments.

Furthermore, configurations may not be applied with respect to SIM A 602, but instead the remaining configurations (other than the Pcell config) may be stored, as part of a SIM A 602 inactive-context. Then, the UE may send an RRC reconfiguration complete message (i.e., using a new Pcell configuration) with a piggybacked coordinated leaving message to request coordinated leaving from NW A 606. Such message may indicate to NW A 606 the following information: 1. Partial configurations or no configurations were applied to SIM A 602. More specifically, a partial configurations are applied when a received RRC reconfiguration message includes cell configuration (as shown by block 636, block 632, and arrow 620); or b. no configuration is applied when the received RRC reconfiguration message includes no Pcell configuration and the baseband processor does not apply any configuration to SIM A 602 from the received RRC Reconfiguration message (as shown by block 638, block 634, and arrow 622); and 2. Coordinated leaving has to occur. Finally, the last few steps again include: 1. NW A 606 sending an RRC Release to SIM A 602 (via the baseband processor), as represented by arrow 624; 2. SIM A 602 transitioning to idle mode, as represented by block 626 and arrow 628; and 3. The baseband processor starting connection establishment corresponding to SIM B 604 by sending an RRC Request, as represented by arrow 630.

The third detailed solution includes the UE (and ultimately, the baseband processor) determining whether to abort the RRC reconfiguration procedure or to leave after completing the RRC reconfiguration procedure. In particular, the UE may decide which option to execute conditionally based on the content of the RRC reconfiguration message. For instance, the UE may consider: 1. Completing the RRC reconfiguration and then sending a coordinated leaving message, which may be beneficial for the UE in cases when the UE is performing a handover via the received RRC reconfiguration procedure; and 2. Aborting the RRC reconfiguration and then sending a coordinated leaving message, which is beneficial for the UE from a latency perspective to establish an RRC Connection for pending high priority activity on a second SIM (e.g., SIM B 604) in cases when reconfiguration is for a reason other than a handover.

The fourth detailed solution may be applicable to each of the three detailed solutions above and is related to a timer-coordinated leaving wait time for an implicit connection release. In other words, regardless of whether the baseband processor completes the connected mode procedure associated with SIM A 702 and triggered by NW A 706 and performs coordinated leaving, or aborts the ongoing connected mode procedure (i.e., of the SIM A 702) and triggers coordinated leaving, the fourth detailed solution can be used to implicitly transition to idle mode (i.e., leave) without having an explicit connection release from the NW.

As illustrated in FIG. 7 , in the fourth detailed solution, SIM A 702 and SIM B 704 may each initially be in an idle/inactive state (as represented by block 710 and block 712, respectively). The baseband processor may then send an RRC request associated with SIM A 702 to NW A 706, as represented by arrow 714. NW A 706 may then send an RRC setup message to SIM A 702 (i.e., via the baseband processor) followed by an RRC complete response to NW A 706 (i.e., via the baseband processor), as represented by arrow 716 and arrow 718, respectively. SIM A 702 may then be in a connected state with NW A 706, as represented by block 720 and block 722.

As represented by block 724, NW A 706 may process various capabilities corresponding to SIM A 702, including a determination that SIM A 702 comprises a MUSIM device. Upon determining that SIM A 702 comprises a MUSIM device, NW A 706 configures timer “coordinatedLeavingWaitTime” when SIM A 702 enters connected mode, as represented by arrow 726 and block 744. In other words, NW A 706 provides the timer in an RRC reconfiguration immediately after an RRC connection is established and the UE capability exchanged (i.e., upon knowing that the UE is an MUSIM UE).

Once again, the baseband processor may be processing a received RRC reconfiguration when paging from NW B 708 to SIM B 704 (via the baseband processor) occurs, as represented by arrow 726 and arrow 728, respectively. In response to the paging received in association with SIM B 704, SIM B 704 may send a suspend request to SIM A 702 (each action of which is ultimately handled by the baseband processor), as represented by arrow 730. The baseband processor may then signal coordinated leaving associated with SIM A 702 to NW A 706, as represented by arrow 732. Notably, the generated timer, “coordinatedLeavingWaitTime,” may be configured to allow SIM A 702 to be transitioned to idle mode (implicitly) after the baseband processor sends the coordinated leaving message associated with SIM A 702 via an RRC request, an RRC reestablishment, or a UAI message without waiting for NW A 706 to send an RRC Release. NW A 706 may start the timer upon reception of the coordinated leaving message. Upon expiration of the timer. NW A 706 may assume that SIM A 702 has transition ed to idle mode and then release the RRC connection locally, as represented by block 734, block 736, block 738, and arrow 740. The baseband processor may then start connection establishment associated with SIM B 704 by sending an RRC Request, as represented by arrow 742.

Accordingly, as described in the above detailed solutions, RRC reconfiguration procedures occurring in association with a first SIM of a MUSIM during receipt of a high priority event associated with a second SIM of the MUSIM UE may include: 1. Aborting the RRC reconfiguration procedure immediately; 2. Completing the RRC reconfiguration procedure normally; 3. Completing the RRC reconfiguration procedure normally with a busy signal on the other SIM; or 4. Partially completing the RRC reconfiguration procedure (applying only mandatory configurations defined by 3GPP, if any).

In addition, as described in the above detailed solutions, coordinated leaving may be triggered by: 1. Piggybacking a coordinated leaving request on a reconfiguration complete message; 2. Sending UAI with a coordinated leaving cause; 3, Sending an RRC reestablishment request with a coordinated leaving cause; or 4. Defining a new RRC signaling message to convey a coordinated leaving request.

Furthermore, as described in the above detailed solutions, the amount of time a UE is to wait for receiving feedback from the NW after sending a coordinated leaving request includes the following options: 1. The UE has to wait for NW feedback (e.g., RRC release); or 2. A max wait-time is configured by a NW configuration parameter (e.g., “coordinatedLeavingWaitTime”), the expiration of which triggers the UE to implicitly move to idle mode.

In this way, MUSIM UEs' actions during concurrent RRC processing on multiple USIMs may be well defined such that a connected mode SIM (e.g., USIM) can signal coordinated leaving (i.e., via the baseband processor) to a network even when the SIM is in the middle of an RRC procedure. Thus, enabling another SIM of the same MUSIM UE to establish an RRC Connection (via the baseband processor) with minimal delay and address corresponding high priority activities. Notably, while the solutions discussed herein generally relate to application of coordinated leaving at the AS layer, similar principles can be utilized when application occurs at the NAS layer.

FIG. 8 illustrates a flowchart of a method for coordinated leaving corresponding to a MUSIM UE. In block 802, the method 800 decodes, at a baseband processor, a radio resource control (RRC) reconfiguration message received from a first network and corresponding to the first SIM. For instance, the RRC reconfiguration may be in regards to a handover procedure. In block 804, the method 800 decodes, at a baseband processor, a communication received from a second network and corresponding to the second SIM while the baseband processor is processing the received RRC reconfiguration message. For instance, the received communication may comprise paging from the second network. Notably, the first network and the second network may be the same network or different networks.

In block 806, the method 800 determines that the communication received from the second network comprises a higher priority than the RRC reconfiguration procedure of the first SIM. For instance, a paging message received in association with the second SIM may be considered a higher priority than the ongoing RRC reconfiguration procedure of the first SIM. In block 808, the method 800, based on determining that the communication received from the second network comprises the higher priority, encodes, at the baseband processor, a LTE assistance information (UAI) message corresponding to the first SIM for transmission to the first network. The UAI message may be configured to inform the first network of coordinated leaving and abortion of the RRC reconfiguration procedure. In block 810, the method 800 transitions the first SIM to an idle mode. For instance, the first SIM may be transitioned to an idle mode in response to receiving an RRC release message from the first network. In block 812, the method 800 encodes, at the baseband processor, an RRC request corresponding to the second SIM for transmission to the second network. For instance, the second SIM may be taking the first steps toward creating a connection with the second network.

FIG. 9 illustrates a flowchart of a method for coordinated leaving corresponding to a MUSIM UE. In block 902, the method 900 decodes, at the baseband processor, a radio resource control (RRC) reconfiguration message received from a first network and corresponding to the first SIM. For instance, the RRC reconfiguration may be in regards to a handover procedure. In block 904, the method 900 decodes, at the baseband processor, a communication received from a second network and corresponding to the second SIM while the baseband processor is processing the received RRC reconfiguration message. For instance, the received communication may comprise paging from the second network. In block 906, the method 900 determines that the communication received from the second network comprises a higher priority than the RRC reconfiguration procedure of the first SIM. For instance, a paging message received in association with the second SIM may be considered a higher priority than the ongoing RRC reconfiguration procedure of the first SIM.

In block 908, the method 900, based on determining that the communication received from the second network comprises the higher priority, encodes, at the baseband processor, a coordinated leaving communication corresponding to the first SIM for transmission to the first network. For instance, such encoded message may comprise an RRC reconfiguration complete message with a piggybacked coordinated leaving message or a UAI with a coordinated leaving cause. In block 910, the method 900 transitions the first SIM to an idle mode. For instance, the first SIM may be transitioned to an idle mode in response to receiving an RRC release message from the first network. In block 912, the method 900 encodes, at the baseband processor, an RRC request corresponding to the second SIM for transmission to the second network. For instance, the baseband processor may be taking the first steps toward creating a connection with the second network and the second SIM.

FIG. 10 illustrates a flowchart of a method for coordinated leaving corresponding to a MUSIM UE. In block 1002, the method 1000 decodes, at a baseband processor, a radio resource control (RRC) reconfiguration message received from a first network and corresponding to the first SIM. For instance, the RRC reconfiguration may be in regards to a handover procedure. In block 1004, the method 1000 decodes, at the baseband processor, a communication received from a second network and corresponding to the second SIM while the baseband processor is processing the received RRC reconfiguration message. For instance, the received communication may comprise paging from the second network. In block 1006, the method 1000 determines that the communication received from the second network comprises a higher priority than the RRC reconfiguration procedure of the first SIM. For instance, a paging associated with the second SIM may be determined to be a higher priority than an RRC reconfiguration associated with the first SIM.

In block 1008, the method 1000, in response to determining that the communication received from the second network comprises a higher priority, processes a context of the RRC reconfiguration procedure of the first SIM. For instance, a context corresponding to a handover may be particularly high priority such that RRC reconfiguration is to be completed. In block 1010, the method 1000 completes the RRC reconfiguration corresponding to the first SIM when the context corresponds to a handover procedure. Completing the RRC reconfiguration may include informing the first network of coordinated leaving.

In block 1012, the method 1000 aborts the RRC reconfiguration corresponding to the first SIM when the context corresponds to anything other than a handover procedure. Aborting the RRC reconfiguration includes informing the first network of coordinated leaving. In block 1014, the method 1000 transitions the first SIM to an idle mode. In block 1016, the method 1000 encodes, at the baseband processor, an RRC request corresponding to the second SIM for transmission to the second network.

FIG. 11 illustrates an example architecture of a system 1100 of a network, in accordance with various embodiments. The following description is provided for an example system 1100 that operates in conjunction with the LTE system standards and 5G or NR system standards as provided by 3GPP technical specifications. However, the example embodiments are not limited in this regard and the described embodiments may apply to other networks that benefit from the principles described herein, such as future 3GPP systems (e.g., Sixth Generation (6G)) systems, IEEE 802.16 protocols (e.g., WMAN, WiMAX, etc.), or the like.

As shown by FIG. 11 , the system 1100 includes UE 1122 and UE 1120. In this example, the UE 1122 and the UE 1120 are illustrated as smartphones (e.g., handheld touchscreen mobile computing devices connectable to one or more cellular networks), but may also comprise any mobile or non-mobile computing device, such as consumer electronics devices, cellular phones, smartphones, feature phones, tablet computers, wearable computer devices, personal digital assistants (PDAs), pagers, wireless handsets, desktop computers, laptop computers, in-vehicle infotainment (IVI), in-car entertainment (ICE) devices, an Instrument Cluster (IC), head-up display (HUD) devices, onboard diagnostic (OBD) devices, dashtop mobile equipment (DME), mobile data terminals (MDTs), Electronic Engine Management System (EEMS), electronic/engine control units (ECUs), electronic/engine control modules (ECMs), embedded systems, microcontrollers, control modules, engine management systems (EMS), networked or “smart” appliances, MTC devices, M2M, IoT devices, and/or the like.

In some embodiments, the UE 1122 and/or the UE 1120 may be IoT UEs, which may comprise a network access layer designed for low power IoT applications utilizing short-lived UE connections. An IoT UE can utilize technologies such as M2M or MTC for exchanging data with an MTC server or device via a PLMN, ProSe or D2D communication, sensor networks, or IoT networks. The M2M or MTC exchange of data may be a machine-initiated exchange of data. An IoT network describes interconnecting IoT UEs, which may include uniquely identifiable embedded computing devices (within the Internet infrastructure), with short-lived connections. The IoT UEs may execute background applications (e.g., keep-alive messages, status updates, etc.) to facilitate the connections of the IoT network.

The UE 1122 and UE 1120 may be configured to connect, for example, communicatively couple, with an access node or radio access node (shown as (R)AN 1108). In embodiments, the (R)AN 1108 may be an NG RAN or a SG RAN, an E-UTRAN, or a legacy RAN, such as a UTRAN or GERAN. As used herein, the term “NG RAN” or the like may refer to a (R)AN 1108 that operates in an NR or SG system, and the term “E-UTRAN” or the like may refer to a (R)AN 1108 that operates in an LTE or 4G system. The UE 1122 and UE 1120 utilize connections (or channels) (shown as connection 1104 and connection 1102, respectively), each of which comprises a physical communications interface or layer (discussed in further detail below).

In this example, the connection 1104 and connection 1102 are air interfaces to enable communicative coupling, and can be consistent with cellular communications protocols, such as a GSM protocol, a CDMA network protocol, a PTT protocol, a POC protocol, a UMTS protocol, a 3GPP LTE protocol, a SG protocol, a NR protocol, and/or any of the other communications protocols discussed herein. In embodiments, the UE 1122 and UE 1120 may directly exchange communication data via a ProSe interface 1110. The ProSe interface 1110 may alternatively be referred to as a sidelink (SL) interface 110 and may comprise one or more logical channels, including but not limited to a PSCCH, a PSSCH, a PSDCH, and a PSBCH.

The UE 1120 is shown to be configured to access an AP 1112 (also referred to as “WLAN node,” “WLAN,” “WLAN Termination,” “WT” or the like) via connection 1124. The connection 1124 can comprise a local wireless connection, such as a connection consistent with any IEEE 802.11 protocol, wherein the AP 1112 would comprise a wireless fidelity (Wi-Fi®) router. In this example, the AP 1112 may be connected to the Internet without connecting to the core network of the wireless system (described in further detail below). In various embodiments, the UE 1120, (R)AN 1108, and AP 1112 may be configured to utilize LWA operation and/or LWIP operation. The LWA operation may involve the UE 1120 in RRC_CONNECTED being configured by the RAN node 1114 or the RAN node 1116 to utilize radio resources of LTE and WLAN. LWIP operation may involve the UE 1120 using WLAN radio resources (e.g., connection 1124) via IPsec protocol tunneling to authenticate and encrypt packets (e.g., IP packets) sent over the connection 1124. IPsec tunneling may include encapsulating the entirety of original IP packets and adding a new packet header, thereby protecting the original header of the IP packets.

The (R)AN 1108 can include one or more AN nodes, such as RAN node 1114 and RAN node 1116, that enable the connection 1104 and connection 1102. As used herein, the terms “access node,” “access point,” or the like may describe equipment that provides the radio baseband functions for data and/or voice connectivity between a network and one or more users. These access nodes can be referred to as BS, gNBs, RAN nodes, eNBs, NodeBs, RSUs TRxPs or TRPs, and so forth, and can comprise ground stations (e.g., terrestrial access points) or satellite stations providing coverage within a geographic area (e.g., a cell). As used herein, the term “NG RAN node” or the like may refer to a RAN node that operates in an NR or SG system (for example, a gNB), and the term “E-UTRAN node” or the like may refer to a RAN node that operates in an LTE or 4G system 1100 (e.g., an eNB). According to various embodiments, the RAN node 1114 or RAN node 1116 may be implemented as one or more of a dedicated physical device such as a macrocell base station, and/or a low power (LP) base station for providing femtocells, picocells or other like cells having smaller coverage areas, smaller user capacity, or higher bandwidth compared to macrocells.

In some embodiments, all or parts of the RAN node 1111 or RAN node 1116 may be implemented as one or more software entities running on server computers as part of a virtual network, which may be referred to as a CRAN and/or a virtual baseband unit pool (vBBUP). In these embodiments, the CRAN or vBBUP may implement a RAN function split, such as a PDCP split wherein RRC and PDCP layers are operated by the CRAN/vBBUP and other L2 protocol entities are operated by individual RAN nodes (e.g., RAN node 1114 or RAN node 1116); a MAC/PHY split wherein RRC, PDCP, RLC, and MAC layers are operated by the CRAN/vBBUP and the PHY layer is operated by individual RAN nodes (e.g., RAN node 1114 or RAN node 1116); or a “lower PHY” split wherein RRC, PDCP, RLC, MAC layers and upper portions of the PHY layer are operated by the CRAM/vBBUP and lower portions of the PHY layer are operated by individual RAN nodes. This virtualized framework allows the freed-up processor cores of the RAN node 1114 or RAN node 1116 to perform other virtualized applications. In some implementations, an individual RAN node may represent individual gNB DUs that are connected to a gNB-CU via individual F1 interfaces (not shown by FIG. 11 ). In these implementations, the gNB-DUs may include one or more remote radio heads or RFEMs, and the gNB-CU may be operated by a server that is located in the (R)AN 1108 (not shown) or by a server pool in a similar manner as the CRAN/vBBUP. Additionally, or alternatively, one or more of the RAN node 1114 or RAN node 1116 may be next generation eNBs (ng-eNBs), which are RAN nodes that provide E-UTRA user plane and control plane protocol terminations toward the UE 1122 and UE 1120, and are connected to an SOC via an NG interface (discussed infra). In V2X scenarios one or more of the RAN node 1114 or RAN node 1116 may be or act as RSUs.

The term “Road Side Unit” or “RSU” may refer to any transportation infrastructure entity used for V2X communications. An RSU may be implemented in or by a suitable RAN node or a stationary (or relatively stationary) UE, where an RSU implemented in or by a UE may be referred to as a “UE-type RSU,” an RSU implemented in or by an eNB may be referred to as an “eNB-type RSU,” an RSU implemented in or by a gNB may be referred to as a “gNB type RSU,” and the like. In one example, an RSU is a computing device coupled with radio frequency circuitry located on a roadside that provides connectivity support to passing vehicle UEs (vUEs). The RSU may also include internal data storage circuitry to store intersection map geometry, traffic statistics, media, as well as applications/software to sense and control ongoing vehicular and pedestrian traffic. The RSU may operate on the 5.9 GHz Direct Short Range Communications (DSRC) band to provide very low latency communications required for high speed events, such as crash avoidance, traffic warnings, and the like. Additionally, or alternatively, the RSU may operate on the cellular V2X band to provide the aforementioned low latency communications, as well as other cellular communications services. Additionally, or alternatively, the RSU may operate as a Wi-Fi hotspot (2.4 GHz band) and/or provide connectivity to one or more cellular networks to provide uplink and downlink communication. The computing device(s) and some or all of the radio frequency circuitry of the RSU may be packaged in a weatherproof enclosure suitable for outdoor installation, and may include a network interface controller to provide a wired connection (e.g., Ethernet) to a traffic signal controller and/or a backhaul network.

The RAN node 1114 and/or the RAN node 1116 can terminate the air interface protocol and can be the first point of contact for the UE 1122 and UE 1120. In some embodiments, the RAN node 1114 and/or the RAN node 1116 can fulfill various logical functions for the (R)AN 1108 including, but not limited to, radio network controller (RNC) functions such as radio bearer management, uplink and downlink dynamic radio resource management and data packet scheduling, and mobility management.

In embodiments, the UE 1122 and UE 1120 can be configured to communicate using OFDM communication signals with each other or with the RAN node 1114 and/or the RAN node 1116 over a multicarrier communication channel in accordance with various communication techniques, such as, but not limited to, an OFDMA communication technique (e.g., for downlink communications) or a SC-FDMA communication technique (e.g., for uplink and ProSe or sidelink communications), although the scope of the embodiments is not limited in this respect. The OFDM signals can comprise a plurality of orthogonal subcarriers.

In some embodiments, a downlink resource grid can be used for downlink transmissions from the RAN node 1114 and/or the RAN node 1116 to the UE 1122 and UE 1120, while uplink transmissions can utilize similar techniques. The grid can be a time-frequency grid, called a resource grid or time-frequency resource grid, which is the physical resource in the downlink in each slot. Such a time-frequency plane representation is a common practice for OFDM systems, which makes it intuitive for radio resource allocation. Each column and each row of the resource grid corresponds to one OFDM symbol and one OFDM subcarrier, respectively. The duration of the resource grid in the time domain corresponds to one slot in a radio frame. The smallest time-frequency unit in a resource grid is denoted as a resource element. Each resource grid comprises a number of resource blocks, which describe the mapping of certain physical channels to resource elements. Each resource block comprises a collection of resource elements; in the frequency domain, this may represent the smallest quantity of resources that currently can be allocated. There are several different physical downlink channels that are conveyed using such resource blocks.

According to various embodiments, the UE 1122 and UE 1120 and the RAN node 1114 and/or the RAN node 1116 communicate data (for example, transmit and receive) over a licensed medium (also referred to as the “licensed spectrum” and/or the “licensed band”) and an unlicensed shared medium (also referred to as the “unlicensed spectrum” and/or the “unlicensed band”). The licensed spectrum may include channels that operate in the frequency range of approximately 400 MHz to approximately 3.8 GHz, whereas the unlicensed spectrum may include the 5 GHz band.

To operate in the unlicensed spectrum, the UE 1122 and UE 1120 and the RAN node 1114 or RAN node 1116 may operate using LAA, eLAA, and/or feLAA mechanisms. In these implementations, the UE 1122 and UE 1120 and the RAN node 1114 or RAN node 1116 may perform one or more known medium-sensing operations and/or carrier-sensing operations in order to determine whether one or more channels in the unlicensed spectrum is unavailable or otherwise occupied prior to transmitting in the unlicensed spectrum. The medium/carrier sensing operations may be performed according to a listen-before-talk (LBT) protocol.

LBT is a mechanism whereby equipment (for example, UE 1122 and UE 1120, RAN node 1114 or RAN node 1116, etc.) senses a medium (for example, a channel or carrier frequency) and transmits when the medium is sensed to be idle (or when a specific channel in the medium is sensed to be unoccupied). The medium sensing operation may include CCA, which utilizes at least ED to determine the presence or absence of other signals on a channel in order to determine if a channel is occupied or clear. This LBT mechanism allows cellular/LAA networks to coexist with incumbent systems in the unlicensed spectrum and with other LAA networks. ED may include sensing RF energy across an intended transmission band for a period of time and comparing the sensed RF energy to a predefined or configured threshold.

Typically, the incumbent systems in the 5 GHz band are WLANs based on IEEE 802.11 technologies. WLAN employs a contention-based channel access mechanism, called CSMA/CA Here, when a WLAN node (e.g., a mobile station (MS) such as LTE 1122, AP 1112, or the like) intends to transmit, the WLAN node may first perform CCA before transmission. Additionally, a backoff mechanism is used to avoid collisions in situations where more than one WLAN node senses the channel as idle and transmits at the same time. The backoff mechanism may be a counter that is drawn randomly within the CWS, which is increased exponentially upon the occurrence of collision and reset to a minimum value when the transmission succeeds. The LBT mechanism designed for LAA is somewhat similar to the CSMA/CA of WLAN. In some implementations, the LBT procedure for DL or UL transmission bursts including PDSCH or PUSCH transmissions, respectively, may have an LAA contention window that is variable in length between X and Y ECCA slots, where X and Y are minimum and maximum values for the CWSs for LAA. In one example, the minimum CWS for an LAA transmission may be 9 microseconds (μs); however, the size of the CWS and a MCOT (for example, a transmission burst) may be based on governmental regulatory requirements.

The LAA mechanisms are built upon CA technologies of LTE-Advanced systems. In CA, each aggregated carrier is referred to as a CC. A CC may have a bandwidth of 1.4, 3, 5, 10, 15 or 20 MHz and a maximum of five CCs can be aggregated, and therefore, a maximum aggregated bandwidth is 100 MHz. In FDD systems, the number of aggregated carriers can be different for DL and UL, where the number of LT CCs is equal to or lower than the number of DL component carriers. In some cases, individual CCs can have a different bandwidth than other CCs. In TDD systems, the number of CCs as well as the bandwidths of each CC is usually the same for DL and UL.

CA also comprises individual serving cells to provide individual CCs. The coverage of the serving cells may differ, for example, because CCs on different frequency bands will experience different pathloss. A primary service cell or PCell may provide a PCC for both UL and DL, and may handle RRC and NAS related activities. The other serving cells are referred to as SCells, and each SCell may provide an individual SCC for both UL and DL. The SCCs may be added and removed as required, while changing the PCC may require the UE 1122 to undergo a handover. In LAA, eLAA, and feLAA, some or all of the SCells may operate in the unlicensed spectrum (referred to as “LAA SCells”), and the LAA SCells are assisted by a PCell operating in the licensed spectrum. When a UE is configured with more than one LAA SCell, the UE may receive UL grants on the configured LAA SCells indicating different PUSCH starting positions within a same subframe.

The PDSCH carries user data and higher-layer signaling to the UE 1122 and UE 1120. The PDCCH carries information about the transport format and resource allocations related to the PDSCH channel, among other things. It may also inform the UE 1122 and UE 1120 about the transport format, resource allocation, and HARQ information related to the uplink shared channel. Typically, downlink scheduling (assigning control and shared channel resource blocks to the UE 1120 within a cell) may be performed at any of the RAN node 1114 or RAN node 1116 based on channel quality information fed back from any of the UE 1122 and UE 1120, The downlink resource assignment information may be sent on the PDCCH used for (e.g., assigned to) each of the UE 1122 and UE 1120.

The PDCCH uses CCEs to convey the control information. Before being mapped to resource elements, the PDCCH complex-valued symbols may first be organized into quadruplets, which may then be permuted using a sub-block interleaver for rate matching. Each PDCCH may be transmitted using one or more of these CCEs, where each CCE may correspond to nine sets of four physical resource elements known as REGs. Four Quadrature Phase Shift Keying (QPSK) symbols may be mapped to each REG. The PDCCH can be transmitted using one or more CCEs, depending on the size of the DCI and the channel condition. There can be four or more different PDCCH formats defined in LTE with different numbers of CCEs (e.g., aggregation level, L=1, 2, 4, or 8).

Some embodiments may use concepts for resource allocation for control channel information that are an extension of the above-described concepts. For example, some embodiments may utilize an EPDCCH that uses PDSCH resources for control information transmission. The EPDCCH may be transmitted using one or more ECCEs. Similar to above, each ECCE may correspond to nine sets of four physical resource elements known as an EREGs. An ECCE may have other numbers of EREGs in some situations.

The RAN node 1114 or RAN node 1116 may be configured to communicate with one another via interface 1130. In embodiments where the system 1100 is an LTE system (e.g., when CN 1106 is an EPC), the interface 1130 may be an X2 interface. The X2 interface may be defined between two or more RAN nodes (e.g., two or more eNBs and the like) that connect to an EPC, and/or between two eNBs connecting to the EPC. In some implementations, the X2 interface may include an X2 user plane interface (X2-U) and an X2 control plane interface (X2-C). The X2-U may provide flow control mechanisms for user data packets transferred over the X2 interface, and may be used to communicate information about the delivery of user data between eNBs. For example, the X2-U may provide specific sequence number information for user data transferred from a MeNB to an SeNB; information about successful in sequence delivery of PDCP PDUs to a UE 1122 from an SeNB for user data; information of PDCP PDUs that were not delivered to a UE 1122; information about a current minimum desired buffer size at the Se NB for transmitting to the UE user data; and the like. The X2-C may provide intra-LTE access mobility functionality, including context transfers from source to target eNBs, user plane transport control, etc.; load management functionality; as well as inter-cell interference coordination functionality.

In embodiments where the system 1100 is a SG or NR system (e.g., when CN 1106 is an SGC), the interface 1130 may be an Xn interface. The Xn interface is defined between two or more RAN nodes (e.g., two or more gNBs and the like) that connect to SGC, between a RAN node 1114 (e.g., a gNB) connecting to SGC and an eNB, and/or between two eNBs connecting to SGC (e.g., CN 1106). In some implementations, the Xn interface may include an Xn user plane (Xn-U) interface and an Xn control plane (Xn-C) interface. The Xn-U may provide non-guaranteed delivery of user plane PDUs and support/provide data forwarding and flow control functionality. The Xn-C may provide management and error handling functionality, functionality to manage the Xn-C interface; mobility support for UE 1122 in a connected mode (e.g., CM-CONNFCTED) including functionality to manage the UE mobility for connected mode between one or more RAN node 1114 or RAN node 1116. The mobility support may include context transfer from an old (source) serving RAN node 1114 to new (target) serving RAN node 1116; and control of user plane tunnels between old (source) serving RAN node 1114 to new (target) serving RAN node 1116. A protocol stack of the Xn-U may include a transport network layer built on Internet Protocol (IP) transport layer, and a GTP-U layer on top of a UDP and/or IP layer(s) to carry user plane PDUs. The Xn-C protocol stack may include an application layer signaling protocol (referred to as Xn Application Protocol (Xn-AP)) and a transport network layer that is built on SCTP. The SCTP may be on top of an IP layer, and may provide the guaranteed delivery of application layer messages. In the transport IP layer, point-to-point transmission is used to deliver the signaling PDUs. In other implementations, the Xn-U protocol stack and/or the Xn-C protocol stack may be same or similar to the user plane and/or control plane protocol stack(s) shown and described herein.

The (R)AN 1108 is shown to be communicatively coupled to a core network—in this embodiment. CN 1106. The CN 1106 may comprise one or more network elements 1132, which are configured to offer various data and telecommunications services to customers/subscribers (e.g., users of UE 1122 and UE 1120) who are connected to the CN 1106 via the (R)AN 1108. The components of the CN 1106 may be implemented in one physical node or separate physical nodes including components to read and execute instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium). In some embodiments, MTV may be utilized to virtualize any or all of the above-described network node functions via executable instructions stored in one or more computer-readable storage mediums (described in further detail below). A logical instantiation of the CN 1106 may be referred to as a network slice, and a logical instantiation of a portion of the CN 1106 may be referred to as a network sub-slice. NFV architectures and infrastructures may be used to virtualize one or more network functions, alternatively performed by proprietary hardware, onto physical resources comprising a combination of industry-standard server hardware, storage hardware, or switches. In other words, NFV systems can be used to execute virtual or reconfigurable implementations of one or more EPC components/functions.

Generally, an application server 1118 may be an element offering applications that use IP bearer resources with the core network (e.g., UMTS PS domain, LTE PS data services, etc.). The application server 1118 can also be configured to support one or more communication services (e.g., VoIP sessions, PTT sessions, group communication sessions, social networking services, etc.) for the UE 1122 and UE 1120 via the EPC. The application server 1118 may communicate with the CN 1106 through an IP communications interface 1136.

In embodiments, the CN 1106 may be an SGC, and the (R)AN 116 may be connected with the CN 1106 via an NG interface 1134. In embodiments, the NG interface 1134 may be split into two parts, an NG user plane (NG-U) interface 1126, which carries traffic data between the RAN node 1114 or RAN node 1116 and a UPF, and the S1 control plane (NG-C) interface 1128, which is a signaling interface between the RAN node 1114 or RAN node 1116 and AMFs.

In embodiments, the CN 1106 may be a SG CN, while in other embodiments, the CN 1106 may be an EPC). Where CN 1106 is an EPC, the (R)AN 116 may be connected with the CN 1106 via an S1 interface 1134. In embodiments, the S1 interface 1134 may be split into two parts, an S1 user plane (S1-U) interface 1126, which carries traffic data between the RAN node 1114 or RAN node 1116 and the S-GW, and the S1-MME interface 1128, which is a signaling interface between the RAN node 1114 or RAN node 1116 and MMEs.

FIG. 12 illustrates an example of infrastructure equipment 1200 in accordance with various embodiments. The infrastructure equipment 1200 may be implemented as a base station, radio head, RAN node, AN, application server, and/or any other element/device discussed herein. In other examples, the infrastructure equipment 1200 could be implemented in or by a UE.

The infrastructure equipment 1200 includes application circuitry 1202, baseband circuitry 1204, one or more radio front end module 1206 (RFEM), memory circuitry 1208, power management integrated circuitry (shown as PMIC 1210), power tee circuitry 1212, network controller circuitry 1214, network interface connector 1220, satellite positioning circuitry 1216, and user interface circuitry 1218. In some embodiments, the device infrastructure equipment 1200 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device. For example, said circuitries may be separately included in more than one device for CRAN, vBBU, or other like implementations. Application circuitry 1202 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of low drop-out voltage regulators (LDOs), interrupt controllers, serial interfaces such as SPI, I²C or universal programmable serial interface module, real time clock (RTC), timer-counters including interval and watchdog timers, general purpose input/output (I/O or IO), memory card controllers such as Secure Digital (SD) MultiMediaCard (MMC) or similar, Universal Serial Bus (USB) interfaces, Mobile Industry Processor interface (MIPO) interfaces and Joint Test Access Group (JTAG) test access ports. The processors (or cores) of the application circuitry 1202 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the infrastructure equipment 1200. In some implementations, the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.

The processor(s) of application circuitry 1202 may include, for example, one or more processor cores (CPUs), one or more application processors, one or more graphics processing units (GPUs), one or more reduced instruction set computing (RISC) processors, one or more Acorn RISC Machine (ARM) processors, one or more complex instruction set computing (CISC) processors, one or more digital signal processors (DSP), one or more FPGAs, one or more PLDs, one or more. ASICs, one or more microprocessors or controllers, or any suitable combination thereof. In some embodiments, the application circuitry 1202 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein. As examples, the processor(s) of application circuitry 1202 may include one or more Intel Pentium®, Core®, or Xeon® processor(s); Advanced Micro Devices (AMD) Ryzen® processor(s), Accelerated Processing Units (APUs), or Epyc® processors; ARM-based processor(s) licensed from ARM Holdings, Ltd. such as the ARM Cortex-A family of processors and the ThunderX2® provided by Cavium™, Inc.; a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior P-class processors; and/or the like. In some embodiments, the infrastructure equipment 1200 may not utilize application circuitry 1202, and instead may include a special-purpose processor/controller to process IP data received from an EPC or 5GC, for example.

In some implementations, the application circuitry 1202 may include one or more hardware accelerators, which may be microprocessors, programmable processing devices, or the like. The one or more hardware accelerators may include, for example, computer vision (CV) and/or deep learning (DL) accelerators. As examples, the programmable processing devices may be one or more a field-programmable devices (FPDs) such as field-programmable gate arrays (FPGAs) and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such implementations, the circuitry of application circuitry 1202 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 1202 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up-tables (LUTs) and the like. The baseband circuitry 1204 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.

The user interface circuitry 1218 may include one or more user interfaces designed to enable user interaction with the infrastructure equipment 1200 or peripheral component interfaces designed to enable peripheral component interaction with the infrastructure equipment 1200. User interfaces may include, but are not limited to, one or more physical or virtual buttons (e.g., a reset button), one or more indicators (e.g., light emitting diodes (LEDs)), a physical keyboard or keypad, a mouse, a touchpad, a touchscreen, speakers or other audio emitting devices, microphones, a printer, a scanner, a headset, a display screen or display device, etc. Peripheral component interfaces may include, but are not limited to, a nonvolatile memory port, a universal serial bus (USB) port, an audio jack, a power supply interface, etc.

The radio front end module 1206 may comprise a millimeter wave (mmWave) radio front end module (RFEM) and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mm Wave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical radio front end module 1206, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 1208 may include one or more of volatile memory including dynamic random access memory (DRAM) and/or synchronous dynamic random access memory (SDRAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc., and may incorporate the three-dimensional (3D)cross-point (XPOINT) memories from Intel® and Micron®. The memory circuitry 1208 may be implemented as one or more of solder down packaged integrated circuits, socketed memory modules and plug-in memory cards.

The PMIC 1210 may include voltage regulators, surge protectors, power alarm detection circuitry, and one or more backup power sources such as a battery or capacitor. The power alarm detection circuitry may detect one or more of brown out (under-voltage) and surge (over-voltage) conditions. The power tee circuitry 1212 may provide for electrical power drawn from a network cable to provide both power supply and data connectivity to the infrastructure equipment 1200 using a single cable.

The network controller circuitry 1214 may provide connectivity to a network using a standard network interface protocol such as Ethernet, Ethernet over GRE Tunnels, Ethernet over Multiprotocol Label Switching (MPLS), or some other suitable protocol. Network connectivity may be provided to/from the infrastructure equipment 1200 via network interface connector 1220 using a physical connection, which may be electrical (commonly referred to as a “copper interconnect”), optical, or wireless. The network controller circuitry 1214 may include one or more dedicated processors and/or FPGAs to communicate using one or more of the aforementioned protocols. In some implementations, the network controller circuitry 1214 may include multiple controllers to provide connectivity to other networks using the same or different protocols.

The positioning circuitry 1216 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a global navigation satellite system (GNSS). Examples of navigation satellite constellations (or GNSS) include United States' Global Positioning System (GPS), Russia's Global Navigation System (GLONASS), the European Union's Galileo System, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., Navigation with Indian Constellation (NAVIC), Japan's Quasi-Zenith Satellite System (QZSS), France's Doppler Orbitography and Radio-positioning Integrated by Satellite (DORIS), etc.), or the like. The positioning circuitry 1216 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 1216 may include a Micro-Technology for Positioning, Navigation, and Timing (Micro-PNT) IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry 1216 may also be part of, or interact with, the baseband circuitry 1204 and/or radio front end module 1206 to communicate with the nodes and components of the positioning network. The positioning circuitry 1216 may also provide position data and/or time data to the application circuitry 1202, which may use the data to synchronize operations with various infrastructure, or the like. The components shown by FIG. 12 may communicate with one another using interface circuitry, which may include any number of bus and/or interconnect (IX) technologies such as industry standard architecture (ISA), extended ISA (EISA), peripheral component interconnect (PCI), peripheral component interconnect extended (PCix), PCI express (PCie), or any number of other technologies. The bus/IX may be a proprietary bus, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I²C interface, an SPI interface, point to point interfaces, and a power bus, among others.

FIG. 13 illustrates an example of a platform 1300 in accordance with various embodiments. In embodiments, the computer platform 1300 may be suitable for use as UEs, application servers, and/or any other element/device discussed herein. The platform 1300 may include any combinations of the components shown in the example. The components of platform 1300 may be implemented as integrated circuits (ICs), portions thereof, discrete electronic devices, or other modules, logic, hardware, software, firmware, or a combination thereof adapted in the computer platform 1300, or as components otherwise incorporated within a chassis of a larger system. The block diagram of FIG. 13 is intended to show a high level view of components of the computer platform 1300. However, some of the components shown may be omitted, additional components may be present, and different arrangement of the components shown may occur in other implementations.

Application circuitry 1302 includes circuitry such as, but not limited to one or more processors (or processor cores), cache memory, and one or more of LDOs, interrupt controllers, serial interfaces such as SPI, I²C or universal programmable serial interface module, RTC, timer-counters including interval and watchdog timers, general purpose IO, memory card controllers such as SD MMC or similar, USB interfaces, MIPI interfaces, and JTAG test access ports. The processors (or cores) of the application circuitry 1302 may be coupled with or may include memory/storage elements and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the platform 1300. In some implementations, the memory/storage elements may be on-chip memory circuitry, which may include any suitable volatile and/or non-volatile memory, such as DRAM, SRAM, EPROM, EEPROM, Flash memory, solid-state memory, and/or any other type of memory device technology, such as those discussed herein.

The processor(s) of application circuitry 1302 may include, for example, one or more processor cores, one or more application processors, one or more GPUs, one or more RISC processors, one or more ARM processors, one or more CISC processors, one or more DSP, one or more FPGAs, one or more PLDs, one or more ASICs, one or more microprocessors or controllers, a multithreaded processor, an ultra-low voltage processor, an embedded processor, some other known processing element, or any suitable combination thereof. In some embodiments, the application circuitry 1302 may comprise, or may be, a special-purpose processor/controller to operate according to the various embodiments herein.

As examples, the processor(s) of application circuitry 1302 may include an Intel® Architecture Core™ based processor, such as a Quark™, an Atom™, an i3, an i5, an i7, or an MCU-class processor, or another such processor available from Intel® Corporation. The processors of the application circuitry 1302 may also be one or more of Advanced Micro Devices (AMD) Ryzen® processor(s) or Accelerated Processing Units (APUs); AS-A9 processor(s) from Apple® Inc., Snapdragon™ processor(s) from Qualcomm® Technologies, Inc., Texas Instruments, Inc.® Open Multimedia Applications Platform (OMAP)™ processor(s); a MIPS-based design from MIPS Technologies, Inc. such as MIPS Warrior M-class, Warrior I-class, and Warrior P-class processors; an ARM-based design licensed from ARM Holdings. Ltd., such as the ARM Cortex-A, Cortex-R, and Cortex-M family of processors; or the like. In some implementations, the application circuitry 1302 may be a part of a system on a chip (SoC) in which the application circuitry 1302 and other components are formed into a single integrated circuit, or a single package, such as the Edison™ or Galileo™ SoC boards from Intel® Corporation.

Additionally or alternatively, application circuitry 1302 may include circuitry such as, but not limited to, one or more a field-programmable devices (FPDs) such as FPGAs and the like; programmable logic devices (PLDs) such as complex PLDs (CPLDs), high-capacity PLDs (HCPLDs), and the like; ASICs such as structured ASICs and the like; programmable SoCs (PSoCs); and the like. In such embodiments, the circuitry of application circuitry 1302 may comprise logic blocks or logic fabric, and other interconnected resources that may be programmed to perform various functions, such as the procedures, methods, functions, etc. of the various embodiments discussed herein. In such embodiments, the circuitry of application circuitry 1302 may include memory cells (e.g., erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory, static memory (e.g., static random access memory (SRAM), anti-fuses, etc.)) used to store logic blocks, logic fabric, data, etc. in look-up tables (LUTs) and the like.

The baseband circuitry 1304 may be implemented, for example, as a solder-down substrate including one or more integrated circuits, a single packaged integrated circuit soldered to a main circuit board or a multi-chip module containing two or more integrated circuits.

The radio front end module 1306 may comprise a millimeter wave (mmWave) radio front end module (RFEM) and one or more sub-mmWave radio frequency integrated circuits (RFICs). In some implementations, the one or more sub-mmWave RFICs may be physically separated from the mmWave RFEM. The RFICs may include connections to one or more antennas or antenna arrays, and the RFEM may be connected to multiple antennas. In alternative implementations, both mmWave and sub-mmWave radio functions may be implemented in the same physical radio front end module 1306, which incorporates both mmWave antennas and sub-mmWave.

The memory circuitry 1308 may include any number and type of memory devices used to provide for a given amount of system memory. As examples, the memory circuitry 1308 may include one or more of volatile memory including random access memory (RAM), dynamic RAM (DRAM) and/or synchronous dynamic RAM (SD RAM), and nonvolatile memory (NVM) including high-speed electrically erasable memory (commonly referred to as Flash memory), phase change random access memory (PRAM), magnetoresistive random access memory (MRAM), etc. The memory circuitry 1308 may be developed in accordance with a Joint Electron Devices Engineering Council (JEDEC) low power double data rate (LPDDR)-based design, such as LPDDR2, LPDDR3, LPDDR4, or the like. Memory circuitry 1308 may be implemented as one or more of solder down packaged integrated circuits, single die package (SDP), dual die package (DDP) or quad die package (Q17P), socketed memory modules, dual inline memory modules (DIMMs) including microDIMMs or MiniDIMMs, and/or soldered onto a motherboard via a ball grid array (BGA). In low power implementations, the memory circuitry 1308 maybe on-die memory or registers associated with the application circuitry 1302. To provide for persistent storage of information such as data, applications, operating systems and so forth, memory circuitry 1308 may include one or more mass storage devices, which may include, inter alia, a solid state disk drive (SSDD), hard disk drive (HDD), a microHDD, resistance change memories, phase change memories, holographic memories, or chemical memories, among others. For example, the computer platform 1300 may incorporate the three-dimensional (3D) cross-point (XPOINT) memories from Intel® and Micron®.

The removable memory 1326 may include devices, circuitry, enclosures/housings, ports or receptacles, etc, used to couple portable data storage devices with the platform 1300. These portable data storage devices may be used for mass storage purposes, and may include, for example, flash memory cards (e.g., Secure Digital (SD) cards, microSD cards, xD picture cards, and the like), and USB flash drives, optical discs, external HDDs, and the like.

The platform 1300 may also include interface circuitry (not shown) that is used to connect external devices with the platform 1300. The external devices connected to the platform 1300 via the interface circuitry include sensors 1322 and electro-mechanical components (shown as EMCs 1324), as well as removable memory devices coupled to removable memory 1326.

The sensors 1322 include devices, modules, or subsystems whose purpose is to detect events or changes in its environment and send the information (sensor data) about the detected events to some other a device, module, subsystem, etc. Examples of such sensors include, inter alia, inertia measurement units (IMUs) comprising accelerometers, gyroscopes, and/or magnetometers; microelectromechanical systems (MEMS) or nanoelectromechanical systems (NEMS) comprising 3-axis accelerometers, 3-axis gyroscopes, and/or magnetometers; level sensors; flow sensors; temperature sensors (e.g., thermistors); pressure sensors; barometric pressure sensors; gravimeters; altimeters; image capture devices (e.g., cameras or lensless apertures); light detection and ranging (LiDAR) sensors; proximity sensors (e.g., infrared radiation detector and the like), depth sensors, ambient light sensors, ultrasonic transceivers; microphones or other like audio capture devices; etc.

EMCs 1324 include devices, modules, or subsystems whose purpose is to enable platform 1300 to change its state, position, and/or orientation, or move or control a mechanism or (sub)system. Additionally. EMCs 1324 may be configured to generate and send messages/signaling to other components of the platform 1300 to indicate a current state of the EMCs 1324. Examples of the EMCs 1324 include one or more power switches, relays including electromechanical relays (EMRs) and/or solid state relays (SSRs), actuators (e.g., valve actuators, etc.), an audible sound generator, a visual warning device, motors (e.g., DC motors, stepper motors, etc.), wheels, thrusters, propellers, claws, clamps, hooks, and/or other like electro-mechanical components. In embodiments, platform 1300 is configured to operate one or more EMCs 1324 based on one or more captured events and/or instructions or control signals received from a service provider and/or various clients. In some implementations, the interface circuitry may connect the platform 1300 with positioning circuitry 1316. The positioning circuitry 1316 includes circuitry to receive and decode signals transmitted/broadcasted by a positioning network of a GNSS. Examples of navigation satellite constellations (or GNSS) include United States' GPS, Russia's GLONASS, the European Union's Galileo system, China's BeiDou Navigation Satellite System, a regional navigation system or GNSS augmentation system (e.g., NAVIC), Japan's QZSS, France's DORIS, etc.), or the like. The positioning circuitry 1316 comprises various hardware elements (e.g., including hardware devices such as switches, filters, amplifiers, antenna elements, and the like to facilitate OTA communications) to communicate with components of a positioning network, such as navigation satellite constellation nodes. In some embodiments, the positioning circuitry 1316 may include a Micro-PNT IC that uses a master timing clock to perform position tracking/estimation without GNSS assistance. The positioning circuitry 1316 may also be part of, or interact with, the baseband circuitry 1304 and/or radio front end module 1306 to communicate with the nodes and components of the positioning network. The positioning circuitry 1316 may also provide position data and/or time data to the application circuitry 1302, which may use the data to synchronize operations with various infrastructure (e.g., radio base stations), for turn-by-turn navigation applications, or the like.

In some implementations, the interface circuitry may connect the platform 1300 with Near-Field Communication circuitry (shown as NFC circuitry 1312). The NFC circuitry 1312 is configured to provide contactless, short-range communications based on radio frequency identification (RFID) standards, wherein magnetic field induction is used to enable communication between NFC circuitry 1312 and NFC-enabled devices external to the platform 1300 (e.g., an “NFC touchpoint”). NFC circuitry 1312 comprises an NFC controller coupled with an antenna element and a processor coupled with the NFC controller. The NFC controller may be a chip/IC providing NFC functionalities to the NFC circuitry 1312 by executing NFC controller firmware and an NFC stack The NFC stack may be executed by the processor to control the NFC controller, and the NFC controller firmware may be executed by the NFC controller to control the antenna element to emit short-range RE signals. The RE signals may power a passive NFC tag (e.g., a microchip embedded in a sticker or wristband) to transmit stored data to the NFC circuitry 1312, or initiate data transfer between the NFC circuitry 1312 and another active NFC device (e.g., a smartphone or an NFC-enabled POS terminal) that is proximate to the platform 1300.

The driver circuitry 1318 may include software and hardware elements that operate to control particular devices that are embedded in the platform 1300, attached to the platform 1300, or otherwise communicatively coupled with the platform 1300. The driver circuitry 1318 may include individual drivers allowing other components of the platform 1300 to interact with or control various input/output (I/O) devices that may be present within, or connected to, the platform 1300. For example, driver circuitry 1318 may include a display driver to control and allow access to a display device, a touchscreen driver to control and allow access to a touchscreen interface of the platform 1300, sensor drivers to obtain sensor readings of sensors 1322 and control and allow access to sensors 1322, EMC drivers to obtain actuator positions of the EMCs 1324 and/or control and allow access to the EMCs 1324, a camera driver to control and allow access to an embedded image capture device, audio drivers to control and allow access to one or more audio devices.

The power management integrated circuitry (shown as PMIC 1310) (also referred to as “power management circuitry”) may manage power provided to various components of the platform 1300. In particular, with respect to the baseband circuitry 1304, the PMIC 1310 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMIC 1310 may often be included when the platform 1300 is capable of being powered by a battery 1314, for example, when the device is included in a UE.

In some embodiments, the PMIC 1310 may control, or otherwise be part of, various power saving mechanisms of the platform 1300. For example, if the platform 1300 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the platform 1300 may power down for brief intervals of time and thus save power. If there is no data traffic activity for an extended period of time, then the platform 1300 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The platform 1300 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The platform 1300 may not receive data in this state; in order to receive data, it must transition back to RRC_Connected state. An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

A battery 1314 may power the platform 1300, although in some examples the platform 1300 may be mounted deployed in a fixed location, and may have a power supply coupled to an electrical grid. The battery 1314 may be a lithium ion battery, a metal-air battery, such as a zinc-air battery, an aluminum-air battery, a lithium-air battery, and the like. In some implementations, such as in V2X applications, the battery 1314 may be a typical lead-acid automotive battery.

In some implementations, the battery 1314 may be a “smart battery,” which includes or is coupled with a Battery Management System (BMS) or battery monitoring integrated circuitry. The BMS may be included in the platform 1300 to track the state of charge (SoCh) of the battery 1314. The BMS may be used to monitor other parameters of the battery 1314 to provide failure predictions, such as the state of health (Soft) and the state of function (SoF) of the battery 1314. The BMS may communicate the information of the battery 1314 to the application circuitry 1302 or other components of the platform 1300. The BMS may also include an analog-to-digital (ADC) convertor that allows the application circuitry 1302 to directly monitor the voltage of the battery 1314 or the current flow from the battery 1314. The battery parameters may be used to determine actions that the platform 1300 may perform, such as transmission frequency, network operation, sensing frequency, and the like.

A power block, or other power supply coupled to an electrical grid may be coupled with the BMS to charge the battery 1314. In some examples, the power block may be replaced with a wireless power receiver to obtain the power wirelessly, for example, through a loop antenna in the computer platform 1300. In these examples, a wireless battery charging circuit may be included in the BMS. The specific charging circuits chosen may depend on the size of the battery 1314, and thus, the current required. The charging may be performed using the Airfuel standard promulgated by the Airfuel Alliance, the Qi wireless charging standard promulgated by the Wireless Power Consortium, or the Rezence charging standard promulgated by the Alliance for Wireless Power, among others.

User interface circuitry 1320 includes various input/output (I/O) devices present within, or connected to, the platform 1300, and includes one or more user interfaces designed to enable user interaction with the platform 1300 and/or peripheral component interfaces designed to enable peripheral component interaction with the platform 1300. The user interface circuitry 1320 includes input device circuitry and output device circuitry. Input device circuitry includes any physical or virtual means for accepting an input including, inter alia, one or more physical or virtual buttons (e.g., a reset button), a physical keyboard, keypad, mouse, touchpad, touchscreen, microphones, scanner, headset, and/or the like. The output device circuitry includes any physical or virtual means for showing information or otherwise conveying information, such as sensor readings, actuator position(s), or other like information. Output device circuitry may include any number and/or combinations of audio or visual display, including, inter alia, one or more simple visual outputs/indicators such as binary status indicators (e.g., light emitting diodes (LEDs)) and multi-character visual outputs, or more complex outputs such as display devices or touchscreens (e.g., Liquid Chrystal Displays (LCD), LED displays, quantum dot displays, projectors, etc.), with the output of characters, graphics, multimedia objects, and the like being generated or produced from the operation of the platform 1300. The output device circuitry may also include speakers or other audio emitting devices, printer(s), and/or the like. In some embodiments, the sensors 1322 may be used as the input device circuitry (e.g., an image capture device, motion capture device, or the like) and one or more EMCs may be used as the output device circuitry (e.g., an actuator to provide haptic feedback or the like). In another example, NFC circuitry comprising an NFC controller coupled with an antenna element and a processing device may be included to read electronic tags and/or connect with another NFC-enabled device. Peripheral component interfaces may include, but are not limited to, a non-volatile memory port, a USB port, an audio jack, a power supply interface, etc.

Although not shown, the components of platform 1300 may communicate with one another using a suitable bus or interconnect (IX) technology, which may include any number of technologies, including ISA, EISA, PCI, PCix, PCie, a Time-Trigger Protocol (TTP) system, a FlexRay system, or any number of other technologies. The bus/IX may be a proprietary bus/IX, for example, used in a SoC based system. Other bus/IX systems may be included, such as an I²C interface, an SPI interface, point-to-point interfaces, and a power bus, among others.

FIG. 14 illustrates example components of a device 1400 in accordance with some embodiments. In some embodiments, the device 1400 may include application circuitry 1406, baseband circuitry 1404, Radio Frequency (RF) circuitry (shown as RF circuitry 1402), front-end module (FEM) circuitry (shown as FEM circuitry 1432), one or more antennas 1430, and power management circuitry (PMC) (shown as PMC 1434) coupled together at least as shown. The components of the illustrated device 1400 may be included in a UE or a RAN node. In some embodiments, the device 1400 may include fewer elements (e.g., a RAN node may not utilize application circuitry 1406, and instead include a processor/controller to process IP data received from an EPC). In some embodiments, the device 1400 may include additional elements such as, for example, memory/storage, display, camera, sensor, or input/output (I/O) interface. In other embodiments, the components described below may be included in more than one device (e.g., said circuitries may be separately included in more than one device for Cloud-RAN (C-RAN) implementations).

The application circuitry 1406 may include one or more application processors. For example, the application circuitry 1406 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The processor(s) may include any combination of general-purpose processors and dedicated processors (e.g., graphics processors, application processors, etc.). The processors may be coupled with or may include memory/storage and may be configured to execute instructions stored in the memory/storage to enable various applications or operating systems to run on the device 1400. In some embodiments, processors of application circuitry 1406 may process IP data packets received from an EPC.

The baseband circuitry 1404 may include circuitry such as, but not limited to, one or more single-core or multi-core processors. The baseband circuitry 1404 may include one or more baseband processors or control logic to process baseband signals received from a receive signal path of the RE circuitry 1402 and to generate baseband signals for a transmit signal path of the RF circuitry 1402. The baseband circuitry 1404 may interface with the application circuitry 1406 for generation and processing of the baseband signals and for controlling operations of the RF circuitry 1402. For example, in some embodiments, the baseband circuitry 1404 may include a third generation (3G) baseband processor (3G baseband processor 1408), a fourth generation (4G) baseband processor (4G baseband processor 1410), a fifth generation (5G) baseband processor (5G baseband processor 1412), or other baseband processor(s) 1414 for other existing generations, generations in development or to be developed in the future (e.g., second generation (2G), sixth generation (6G), etc.). The baseband circuitry 1404 (e.g., one or more of baseband processors) may handle various radio control functions that enable communication with one or more radio networks via the RE circuitry 1402. In other embodiments, some or all of the functionality of the illustrated baseband processors may be included in modules stored in the memory 1420 and executed via a Central Processing Unit (CPU 1416). The radio control functions may include, but are not limited to, signal modulation/demodulation, encoding/decoding, radio frequency shifting, etc. In some embodiments, modulation/demodulation circuitry of the baseband circuitry 1404 may include Fast-Fourier Transform (FFT), precoding, or constellation mapping/demapping functionality. In some embodiments, encoding/decoding circuitry of the baseband circuitry 1404 may include convolution, tail-biting convolution, turbo, Viterbi, or Low Density Parity Check (LDPC) encoder/decoder functionality. Embodiments of modulation/demodulation and encoder/decoder functionality are not limited to these examples and may include other suitable functionality in other embodiments.

In some embodiments, the baseband circuitry 1404 may include a digital signal processor (DSP), such as one or more audio DSP(s) 1418. The one or more audio DSP(s) 1418 may include elements for compression/decompression and echo cancellation and may include other suitable processing elements in other embodiments. Components of the baseband circuitry may be suitably combined in a single chip, a single chipset, or disposed on a same circuit board in some embodiments. In some embodiments, some or all of the constituent components of the baseband circuitry 1404 and the application circuitry 1406 may be implemented together such as, for example, on a system on a chip (SOC).

In some embodiments, the baseband circuitry 1404 may provide for communication compatible with one or more radio technologies. For example, in some embodiments, the baseband circuitry 1404 may support communication with an evolved universal terrestrial radio access network (EUTRAN) or other wireless metropolitan area networks (WMAN), a wireless local area network (WLAN), or a wireless personal area network (WPAN). Embodiments in which the baseband circuitry 1404 is configured to support radio communications of more than one wireless protocol may be referred to as multi-mode baseband circuitry.

The RE circuitry 1402 may enable communication with wireless networks using modulated electromagnetic radiation through a non-solid medium. In various embodiments, the RE circuitry 1402 may include switches, filters, amplifiers, etc. to facilitate the communication with the wireless network. The RE circuitry 1402 may include a receive signal path which may include circuitry to down-convert RF signals received from the FEM circuitry 1432 and provide baseband signals to the baseband circuitry 1404. The RE circuitry 1402 may also include a transmit signal path which may include circuitry to up-convert baseband signals provided by the baseband circuitry 1404 and provide RF output signals to the FEM circuitry 1432 for transmission.

In some embodiments, the receive signal path of the RF circuitry 1402 may include mixer circuitry 1422, amplifier circuitry 1424 and filter circuitry 1426. In some embodiments, the transmit signal path of the RF circuitry 1402 may include filter circuitry 1426 and mixer circuitry 1422. The RF circuitry 1402 may also include synthesizer circuitry 1428 for synthesizing a frequency for use by the mixer circuitry 1422 of the receive signal path and the transmit signal path. In some embodiments, the mixer circuitry 1422 of the receive signal path may be configured to down-convert RF signals received from the FEM circuitry 1432 based on the synthesized frequency provided by synthesizer circuitry 1428. The amplifier circuitry 1424 may be configured to amplify the down-converted signals and the filter circuitry 1426 may be a low-pass filter (LPF) or band-pass filter (BPF) configured to remove unwanted signals from the down-converted signals to generate output baseband signals. Output baseband signals may be provided to the baseband circuitry 1404 for further processing. In some embodiments, the output baseband signals may be zero-frequency baseband signals, although this is not a requirement. In some embodiments, the mixer circuitry 1422 of the receive signal path may comprise passive mixers, although the scope of the embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 1422 of the transmit signal path may be configured to up-convert input baseband signals based on the synthesized frequency provided by the synthesizer circuitry 1428 to generate RE output signals for the FEM circuitry 1432. The baseband signals may be provided by the baseband circuitry 1404 and may be filtered by the filter circuitry 1426.

In some embodiments, the mixer circuitry 1422 of the receive signal path and the mixer circuitry 1422 of the transmit signal path may include two or more mixers and may be arranged for quadrature downconversion and upconversion, respectively. In some embodiments, the mixer circuitry 1422 of the receive signal path and the mixer circuitry 1422 of the transmit signal path may include two or more mixers and may be arranged for image rejection (e.g., Hartley image rejection). In some embodiments, the mixer circuitry 1422 of the receive signal path and the mixer circuitry 1422 may be arranged for direct downconversion and direct upconversion, respectively. In some embodiments, the mixer circuitry 1422 of the receive signal path and the mixer circuitry 1422 of the transmit signal path may be configured for super-heterodyne operation.

In some embodiments, the output baseband signals and the input baseband signals may be analog baseband signals, although the scope of the embodiments is not limited in this respect. In some alternate embodiments, the output baseband signals and the input baseband signals may be digital baseband signals. In these alternate embodiments, the RF circuitry 1402 may include analog-to-digital converter (ADC) and digital-to-analog converter (DAC) circuitry and the baseband circuitry 1404 may include a digital baseband interface to communicate with the RF circuitry 1402.

In some dual-mode embodiments, a separate radio IC circuitry may be provided for processing signals for each spectrum, although the scope of the embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 1428 may be a fractional-N synthesizer or a fractional N/N+1 synthesizer, although the scope of the embodiments is not limited in this respect as other types of frequency synthesizers may be suitable. For example, synthesizer circuitry 1428 may be a delta-sigma synthesizer, a frequency multiplier, or a synthesizer comprising a phase-locked loop with a frequency divider.

The synthesizer circuitry 1428 may be configured to synthesize an output frequency for use by the mixer circuitry 1422 of the RF circuitry 1402 based on a frequency input and a divider control input. In some embodiments, the synthesizer circuitry 1428 may be a fractional N/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltage controlled oscillator (VCO), although that is not a requirement. Divider control input may be provided by either the baseband circuitry 1404 or the application circuitry 1406 (such as an applications processor) depending on the desired output frequency. In some embodiments, a divider control input (e.g., N) may be determined from a look-up table based on a channel indicated by the application circuitry 1406.

Synthesizer circuitry 1428 of the RF circuitry 1402 may include a divider, a delay-locked loop (DLL), a multiplexer and a phase accumulator. In some embodiments, the divider may be a dual modulus divider (DMD) and the phase accumulator may be a digital phase accumulator (DPA). In some embodiments, the DMD may be configured to divide the input signal by either N or N+1 (e.g., based on a carry out) to provide a fractional division ratio. In some example embodiments, the DLL may include a set of cascaded, tunable, delay elements, a phase detector, a charge pump and a D-type flip-flop. In these embodiments, the delay elements may be configured to break a VCO period up into Nd equal packets of phase, where Nd is the number of delay elements in the delay line. In this way, the DLL provides negative feedback to help ensure that the total delay through the delay line is one VCO cycle.

In some embodiments, the synthesizer circuitry 1428 may be configured to generate a carrier frequency as the output frequency, while in other embodiments, the output frequency may be a multiple of the carrier frequency (e.g., twice the carrier frequency, four times the carrier frequency) and used in conjunction with quadrature generator and divider circuitry to generate multiple signals at the carrier frequency with multiple different phases with respect to each other. In some embodiments, the output frequency may be a LO frequency (fLO). In some embodiments, the RF circuitry 1402 may include an IQ/polar converter.

The FEM circuitry 1432 may include a receive signal path which may include circuitry configured to operate on RF signals received from one or more antennas 1430, amplify the received signals and provide the amplified versions of the received signals to the RF circuitry 1402 for further processing. The FEM circuitry 1432 may also include a transmit signal path which may include circuitry configured to amplify signals for transmission provided by the RE circuitry 1402 for transmission by one or more of the one or more antennas 1430. In various embodiments, the amplification through the transmit or receive signal paths may be done solely in the RF circuitry 1402, solely in the FEM circuitry 1432, or in both the RF circuitry 1402 and the FEM circuitry 1432.

In some embodiments, the FEM circuitry 1432 may include a TX/RX switch to switch between transmit mode and receive mode operation. The FEM circuitry 1432 may include a receive signal path and a transmit signal path. The receive signal path of the FEM circuitry 1432 may include an LNA to amplify received RF signals and provide the amplified received RF signals as an output (e.g., to the RF circuitry 1402). The transmit signal path of the FEM circuitry 1432 may include a power amplifier (PA) to amplify input RF signals (e.g., provided by the RF circuitry 1402), and one or more filters to generate RF signals for subsequent transmission (e.g., by one or more of the one or more antennas 1430).

In some embodiments, the PMC 1434 may manage power provided to the baseband circuitry 1404. In particular, the PMC 1434 may control power-source selection, voltage scaling, battery charging, or DC-to-DC conversion. The PMC 1434 may often be included when the device 1400 is capable of being powered by a battery, for example, when the device 1400 is included in a UE. The PMC 1434 may increase the power conversion efficiency while providing desirable implementation size and heat dissipation characteristics.

FIG. 14 shows the PMC 1434 coupled only with the baseband circuitry 1404. However, in other embodiments, the PMC 1434 may be additionally or alternatively coupled with, and perform similar power management operations for, other components such as, but not limited to, the application circuitry 1406, the RE circuitry 1402, or the FEM circuitry 1432.

In some embodiments, the PMC 1434 may control, or otherwise be part of, various power saving mechanisms of the device 1400. For example, if the device 1400 is in an RRC_Connected state, where it is still connected to the RAN node as it expects to receive traffic shortly, then it may enter a state known as Discontinuous Reception Mode (DRX) after a period of inactivity. During this state, the device 1400 may power down for brief intervals of time and thus save power.

If there is no data traffic activity for an extended period of time, then the device 1400 may transition off to an RRC_Idle state, where it disconnects from the network and does not perform operations such as channel quality feedback, handover, etc. The device 1400 goes into a very low power state and it performs paging where again it periodically wakes up to listen to the network and then powers down again. The device 1400 may not receive data in this state, and in order to receive data, it transitions back to an RRC_Connected state.

An additional power saving mode may allow a device to be unavailable to the network for periods longer than a paging interval (ranging from seconds to a few hours). During this time, the device is totally unreachable to the network and may power down completely. Any data sent during this time incurs a large delay and it is assumed the delay is acceptable.

Processors of the application circuitry 1406 and processors of the baseband circuitry 1404 may be used to execute elements of one or more instances of a protocol stack. For example, processors of the baseband circuitry 1404, alone or in combination, may be used to execute Layer 3, Layer 2, or Layer 1 functionality, while processors of the application circuitry 1406 may utilize data (e.g., packet data) received from these layers and further execute Layer 4 functionality (e.g., transmission communication protocol (TCP) and user datagram protocol (UDP) layers). As referred to herein, Layer 3 may comprise a radio resource control (RRC) layer, described in further detail below. As referred to herein, Layer 2 may comprise a medium access control (MAC) layer, a radio link control (RLC) layer, and a packet data convergence protocol (PDCP) layer, described in further detail below. As referred to herein, Layer 1 may comprise a physical (PHY) layer of a UE/RAN node, described in further detail below.

FIG. 15 illustrates example interfaces 1500 of baseband circuitry in accordance with some embodiments. As discussed above, the baseband circuitry 1404 of FIG. 14 may comprise 3G baseband processor 1408, 4G baseband processor 1410, 5G baseband processor 1412, other baseband processor(s) 1414, CPU 1416, and a memory 1420 utilized by said processors. As illustrated, each of the processors may include a respective memory interface 1502 to send/receive data to/from the memory 1420.

The baseband circuitry 1404 may further include one or more interfaces to communicatively couple to other circuitries/devices, such as a memory interface 1504 (e.g., an interface to send/receive data to/from memory external to the baseband circuitry 1404), an application circuitry interface 1506 (e.g., an interface to send/receive data to/from the application circuitry 1406 of FIG. 14 ), an RF circuitry interface 1508 (e.g., an interface to send/receive data to/from RE circuitry 1402 of FIG. 14 ), a wireless hardware connectivity interface 1510 (e.g., an interface to send/receive data to/from Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components), and a power management interface 1512 (e.g., an interface to send/receive power or control signals to/from the PMC 1434.

FIG. 16 is a block diagram illustrating components 1600, according to some example embodiments, able to read instructions from a machine-readable or computer-readable medium (e.g., a non-transitory machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 16 shows a diagrammatic representation of hardware resources 1602 including one or more processors 1606 (or processor cores), one or more memory/storage devices 1614, and one or more communication resources 1624, each of which may be communicatively coupled via a bus 1616. For embodiments where node virtualization NFV) is utilized, a hypervisor 1622 may be executed to provide an execution environment for one or more network slices/sub-slices to utilize the hardware resources 1602.

The processors 1606 (e.g., a central processing unit (CPU), a reduced instruction set computing (RISC) processor, a complex instruction set computing (CISC) processor, a graphics processing unit (GPU), a digital signal processor (DSP) such as a baseband processor, an application specific integrated circuit (ASIC), a radio-frequency integrated circuit (RTIC), another processor, or any suitable combination thereof) may include, for example, a processor 1608 and a processor 1610.

The memory/storage devices 1614 may include main memory, disk storage, or any suitable combination thereof. The memory/storage devices 1614 may include, but are not limited to any type of volatile or non-volatile memory such as dynamic random access memory (DRAM), static random-access memory (SRAM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), Flash memory, solid-state storage, etc.

The communication resources 1624 may include interconnection or network interface components or other suitable devices to communicate with one or more peripheral devices 1604 or one or more databases 1620 via a network 1618. For example, the communication resources 1624 may include wired communication components (e.g., for coupling via a Universal Serial Bus (USB)), cellular communication components, NFC components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components.

Instructions 1612 may comprise software, a program, an application, an applet, an app, or other executable code for causing at least any of the processors 1606 to perform any one or more of the methodologies discussed herein. The instructions 1612 may reside, completely or partially, within at least one of the processors 1606 (e.g., within the processor's cache memory), the memory/storage devices 1614, or any suitable combination thereof. Furthermore, any portion of the instructions 1612 may be transferred to the hardware resources 1602 from any combination of the peripheral devices 1604 or the databases 1620. Accordingly, the memory of the processors 1606, the memory/storage devices 1614, the peripheral devices 1604, and the databases 1620 are examples of computer-readable and machine-readable media.

For one or more embodiments, at least one of the components set forth in one or more of the preceding figures may be configured to perform one or more operations, techniques, processes, and/or methods as set forth in the Example Section below. For example, the baseband circuitry as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below. For another example, circuitry associated with a UE, base station, network element, etc. as described above in connection with one or more of the preceding figures may be configured to operate in accordance with one or more of the examples set forth below in the example section.

EXAMPLE SECTION

The following examples pertain to further embodiments.

Example 1 may include a method for wireless communication by a user equipment (UE) having a first subscriber identity module (SIM), a second SIM, and a baseband processor, comprising: decoding, at the baseband processor, a radio resource control (RRC) reconfiguration message received from a first network and corresponding to the first SIM; decoding, at the baseband processor, a communication received from a second network and corresponding to the second SIM while the baseband processor is processing the received RRC reconfiguration message; determining that the communication received from the second network comprises a higher priority than the RRC reconfiguration procedure of the first SIM; based on determining that the communication received from the second network comprises the higher priority, encoding, at the baseband processor, a UE assistance information (UAI) message corresponding to the first SIM for transmission to the first network, the UAI message being configured to inform the first network of coordinated leaving and abortion of the RRC reconfiguration procedure; transitioning the first SIM to an idle mode; and encoding, at the baseband processor, an RRC request corresponding to the second SIM for transmission to the second network.

Example 2 may include the method of example 1, further comprising: decoding, at the baseband processor, a timer from the first network for the first SIM, the timer being included within the decoded RRC reconfiguration message, the message being generated and transmitted by the first network upon identifying the UE has multiple SIMs during a capability exchange upon connection of the first SIM to the first network, the timer including a set amount of time; and transitioning the first SIM to an idle mode when the set amount of time has passed after informing the first network of coordinated leaving.

Example 3 may include the method of example 1, wherein the received RRC reconfiguration message includes a conditional handover.

Example 4 may include a method for wireless communication by a user equipment (UE) having a first subscriber identity module (SIM), a second SIM, and a baseband processor, comprising: decoding, at the baseband processor, a radio resource control (RRC) reconfiguration message received from a first network and corresponding to the first SIM; decoding, at the baseband processor, a communication received from a second network at the second. SIM while the baseband processor is processing the received RRC reconfiguration message; determining that the communication received from the second network comprises a higher priority than the RRC reconfiguration procedure of the first SIM; based on determining that the communication received from the second network comprises the higher priority, encoding, at the baseband processor, a coordinated leaving communication corresponding to the first SIM for transmission to the first network; transitioning the first SIM to an idle mode; and encoding, at the baseband processor, an RRC request corresponding to the second SIM for transmission to the second network.

Example 5 may include the method of example 4, wherein encoding the coordinated leaving communication further comprises piggybacking the encoded coordinated leaving message with an RRC reconfiguration complete message in a transmission to the first network.

Example 6 may include the method of example 4, wherein encoding the coordinated leaving communication further comprises encoding a UE assistance information (UAI) message that includes a coordinated leaving cause.

Example 7 may include the method of example 4, further comprising encoding, at the baseband processor, a busy indication message corresponding to the second SIM for transmission to the second network in response to decoding the communication from the second network corresponding to the second SIM, the busy indication including a timer that is configured to inform the second network of the RRC reconfiguration being handled for the first SIM of the UE and indicate a time period within which the baseband processor will respond to the decoded communication corresponding to the second SIM.

Example 8 may include the method of example 7, wherein encoding the coordinated leaving communication further comprises piggybacking the encoded coordinated leaving message with an RRC reconfiguration complete message in a transmission to the first network.

Example 9 may include the method of example 7, wherein the busy indication is sent using an existing random access channel procedure or a dedicated pre-defined idle configuration.

Example 10 may include the method of example 4, further comprising: decoding one or more configurations corresponding to the RRC reconfiguration procedure of the first SIM; determining that at least one of the one or more configurations comprises a primary cell (Pcell) configuration; applying the at least one Pcell configuration to the first SIM; and storing each of the one or more configurations that does not comprise the Pcell configuration.

Example 11 may include the method of example 10, wherein the at least one Pcell configuration includes a configuration that impacts radio link quality of the UE.

Example 12 may include the method of example 10, wherein encoding the coordinated leaving communication further comprises encoding an RRC reconfiguration complete message corresponding to the first SIM, the message informing the first network that the at least one Pcell configuration was applied and that coordinated leaving is to occur.

Example 13 may include the method of example 11, wherein the coordinated leaving communication is piggybacked on the RRC complete message, the RRC complete message being sent using the at least one Pcell configuration.

Example 14 may include the method of example 4, further comprising: decoding one or more configurations corresponding to the RRC reconfiguration procedure of the first SIM; determining that none of the one or more configurations comprise a primary cell (Pcell) configuration; and storing each of the one or more configurations that does not comprise the Pcell configuration.

Example 15 may include the method of example 14, wherein encoding the coordinated leaving communication further comprises encoding an RRC reconfiguration complete message corresponding to the first SIM, the message informing the first network that no configuration was applied and that coordinated leaving is to occur.

Example 16 may include the method of example 15, wherein the coordinated leaving communication is piggybacked on the RRC complete message, the RRC complete message being sent using the at least one Pcell configuration.

Example 17 may include the method of example 4, further comprising: decoding, at the baseband processor, a tinier from the first network corresponding to the first SIM, the timer being included within the decoded RRC reconfiguration message, the message being generated and transmitted by the first network upon identifying the LTE has multiple SIMs during a capability exchange upon connection of the first SIM to the first network, the timer including a set amount of time; and transitioning the first SIM to an idle mode when the set amount of time has passed after informing the first network of coordinated leaving.

Example 18 may include a method for wireless communication by a user equipment (UE) having a first subscriber identity module (SIM), a second SIM, and a baseband processor, comprising: decoding, at the baseband processor, a radio resource control (RRC) reconfiguration message received from a first network and corresponding to the first SIM; decoding, at the baseband processor, a communication received from a second network and corresponding to the second SIM while the baseband processor is processing the received RRC reconfiguration message; determining that the communication received from the second network comprises a higher priority than the RRC reconfiguration procedure of the first SIM; in response to determining that the communication received from the second network comprises a higher priority, processing a context of the RRC reconfiguration procedure of the first SIM; based on processing the context: completing the RRC reconfiguration corresponding to the first SIM when the context corresponds to a handover procedure, completing the RRC reconfiguration including informing the first network of coordinated leaving; and aborting the RRC reconfiguration corresponding to the first SIM when the context corresponds to anything other than a handover procedure, aborting the RRC reconfiguration including informing the first network of coordinated leaving; transitioning the first SIM to an idle mode; and encoding, at the baseband processor, an RRC request corresponding to the second SIM for transmission to the second network.

Example 19 may include the method of example 18, further comprising: decoding, at the baseband processor, a timer from the first network for the first SIM, the timer being included within the decoded RRC reconfiguration message, the message being generated and transmitted by the first network upon identifying the UE has multiple SIMs during a capability exchange upon connection of the first SIM to the first network, the timer including a set amount of time; and transitioning the first SIM to an idle mode when the set amount of time has passed after informing the first network of coordinated leaving.

Example 20 may include the method of example 19, further comprising receiving a release locally from the first network corresponding to the first SIM.

Example 21 may include an apparatus comprising means to perform one or more elements of a method described in or related to any of the above Examples, or any other method or process described herein.

Example 22 may include one or more non-transitory computer-readable media comprising instructions to cause an electronic device, upon execution of the instructions by one or more processors of the electronic device, to perform one or more elements of a method described in or related to any of the above Examples, or any other method or process described herein.

Example 23 may include an apparatus comprising logic, modules, or circuitry to perform one or more elements of a method described in or related to any of the above Examples, or any other method or process described herein.

Example 24 may include a method, technique, or process as described in or related to any of the above Examples, or portions or parts thereof.

Example 25 may include an apparatus comprising: one or more processors and one or more computer-readable media comprising instructions that, when executed by the one or more processors, cause the one or more processors to perform the method, techniques, or process as described in or related to any of the above Examples, or portions thereof.

Example 26 may include a signal as described in or related to any of the above Examples, or portions or parts thereof.

Example 27 may include a datagram, packet, frame, segment, protocol data unit (PDU), or message as described in or related to any of the above Examples, or portions or parts thereof, or otherwise described in the present disclosure.

Example 28 may include a signal encoded with data as described in or related to any of the above Examples, or portions or parts thereof, or otherwise described in the present disclosure.

Example 29 may include a signal encoded with a datagram, packet, frame, segment, PDU, or message as described in or related to any of the above Examples, or portions or parts thereof, or otherwise described in the present disclosure.

Example 30 may include an electromagnetic signal carrying computer-readable instructions, wherein execution of the computer-readable instructions by one or more processors is to cause the one or more processors to perform the method, techniques, or process as described in or related to any of the above Examples, or portions thereof.

Example 31 may include a computer program comprising instructions, wherein execution of the program by a processing element is to cause the processing element to carry out the method, techniques, or process as described in or related to any of the above Examples, or portions thereof.

Example 32 may include a signal in a wireless network as shown and described herein.

Example 33 may include a method of communicating in a wireless network as shown and described herein.

Example 34 may include a system for providing wireless communication as shown and described herein.

Example 35 may include a device for providing wireless communication as shown and described herein.

Any of the above described examples may be combined with any other example (or combination of examples), unless explicitly stated otherwise. The foregoing description of one or more implementations provides illustration and description, but is not intended to be exhaustive or to limit the scope of embodiments to the precise form disclosed. Modifications and variations are possible in light of the above teachings or may be acquired from practice of various embodiments.

Embodiments and implementations of the systems and methods described herein may include various operations, which may be embodied in machine-executable instructions to be executed by a computer system. A computer system may include one or more general-purpose or special-purpose computers (or other electronic devices). The computer system may include hardware components that include specific logic for performing the operations or may include a combination of hardware, software, and/or firmware.

It should be recognized that the systems described herein include descriptions of specific embodiments. These embodiments can be combined into single systems, partially combined into other systems, split into multiple systems or divided or combined in other ways. In addition, it is contemplated that parameters, attributes, aspects, etc. of one embodiment can be used in another embodiment. The parameters, attributes, aspects, etc. are merely described in one or more embodiments for clarity, and it is recognized that the parameters, attributes, aspects, etc. can be combined with or substituted for parameters, attributes, aspects, etc. of another embodiment unless specifically disclaimed herein.

It is well understood that the use of personally identifiable information should follow privacy policies and practices that are generally recognized as meeting or exceeding industry or governmental requirements for maintaining the privacy of users. In particular, personally identifiable information data should be managed and handled so as to minimize risks of unintentional or unauthorized access or use, and the nature of authorized use should be clearly indicated to users.

Although the foregoing has been described in some detail for purposes of clarity, it will be apparent that certain changes and modifications may be made without departing from the principles thereof. It should be noted that there are many alternative ways of implementing both the processes and apparatuses described herein. Accordingly, the present embodiments are to be considered illustrative and not restrictive, and the description is not to be limited to the details given herein, but may be modified within the scope and equivalents of the appended claims. 

The invention claimed is:
 1. A method for wireless communication by a user equipment (UE) having a first subscriber identity module (SIM), a second SIM, and a baseband processor, comprising: decoding, at the baseband processor, a radio resource control (RRC) reconfiguration message received from a first network and corresponding to the first SIM; decoding, at the baseband processor, a communication received from a second network and corresponding to the second SIM while the baseband processor is processing the received RRC reconfiguration message; determining that the communication received from the second network comprises a higher priority than the RRC reconfiguration procedure of the first SIM; based on determining that the communication received from the second network comprises the higher priority, encoding, at the baseband processor, a UE assistance information (UAI) message corresponding to the first SIM for transmission to the first network, the UAI message being configured to inform the first network of coordinated leaving and abortion of the RRC reconfiguration procedure; transitioning the first SIM to an idle mode; and encoding, at the baseband processor, an RRC request corresponding to the second SIM for transmission to the second network.
 2. The method of claim 1, further comprising: decoding, at the baseband processor, a timer from the first network for the first SIM, the timer being included within the decoded RRC reconfiguration message, the message being generated and transmitted by the first network upon identifying the UE has multiple SIMs during a capability exchange upon connection of the first SIM to the first network, the timer including a set amount of time; and transitioning the first SIM to an idle mode when the set amount of time has passed after informing the first network of coordinated leaving.
 3. The method of claim 1, wherein the received RRC reconfiguration message includes a conditional handover.
 4. A method for wireless communication by a user equipment (UE) having a first subscriber identity module (SIM), a second SIM, and a baseband processor, comprising: decoding, at the baseband processor, a radio resource control (RRC) reconfiguration message received from a first network and corresponding to the first SIM; decoding, at the baseband processor, a communication received from a second network at the second SIM while the baseband processor is processing the received RRC reconfiguration message; determining that the communication received from the second network comprises a higher priority than the RRC reconfiguration procedure of the first SIM; based on determining that the communication received from the second network comprises the higher priority, encoding, at the baseband processor, a coordinated leaving communication corresponding to the first SIM for transmission to the first network; transitioning the first SIM to an idle mode; and encoding, at the baseband processor, an RRC request corresponding to the second SIM for transmission to the second network.
 5. The method of claim 4, wherein encoding the coordinated leaving communication further comprises piggybacking the encoded coordinated leaving message with an RRC reconfiguration complete message in a transmission to the first network.
 6. The method of claim 4, wherein encoding the coordinated leaving communication further comprises encoding a UE assistance information (UAI) message that includes a coordinated leaving cause.
 7. The method of claim 4, further comprising encoding, at the baseband processor, a busy indication message corresponding to the second SIM for transmission to the second network in response to decoding the communication from the second network corresponding to the second SIM, the busy indication including a timer that is configured to inform the second network of the RRC reconfiguration being handled for the first SIM of the UE and indicate a time period within which the baseband processor will respond to the decoded communication corresponding to the second SIM.
 8. The method of claim 7, wherein encoding the coordinated leaving communication further comprises piggybacking the encoded coordinated leaving message with an RRC reconfiguration complete message in a transmission to the first network.
 9. The method of claim 7, wherein the busy indication is sent using an existing random access channel procedure or a dedicated pre-defined idle configuration.
 10. The method of claim 4, further comprising: decoding one or more configurations corresponding to the RRC reconfiguration procedure of the first SIM; determining that at least one of the one or more configurations comprises a primary cell (Pcell) configuration; applying the at least one Pcell configuration to the first SIM; and storing each of the one or more configurations that does not comprise the Pcell configuration.
 11. The method of claim 10, wherein the at least one Pcell configuration includes a configuration that impacts radio link quality of the UE.
 12. The method of claim 10, wherein encoding the coordinated leaving communication further comprises encoding an RRC reconfiguration complete message corresponding to the first SIM, the message informing the first network that the at least one Pcell configuration was applied and that coordinated leaving is to occur.
 13. The method of claim 11, wherein the coordinated leaving communication is piggybacked on the RRC complete message, the RRC complete message being sent using the at least one Pcell configuration.
 14. The method of claim 4, further comprising: decoding one or more configurations corresponding to the RRC reconfiguration procedure of the first SIM; determining that none of the one or more configurations comprise a primary cell (Pcell) configuration; and storing each of the one or more configurations that does not comprise the Pcell configuration.
 15. The method of claim 14, wherein encoding the coordinated leaving communication further comprises encoding an RRC reconfiguration complete message corresponding to the first SIM, the message informing the first network that no configuration was applied and that coordinated leaving is to occur.
 16. The method of claim 15, wherein the coordinated leaving communication is piggybacked on the RRC complete message, the RRC complete message being sent using the at least one Pcell configuration.
 17. The method of claim 4, further comprising: decoding, at the baseband processor, a timer from the first network corresponding to the first SIM, the timer being included within the decoded RRC reconfiguration message, the message being generated and transmitted by the first network upon identifying the UE has multiple SIMS during a capability exchange upon connection of the first SIM to the first network, the timer including a set amount of time; and transitioning the first SIM to an idle mode when the set amount of time has passed after informing the first network of coordinated leaving.
 18. A method for wireless communication by a user equipment (UE) having a first subscriber identity module (SIM), a second SIM, and a baseband processor, comprising: decoding, at the baseband processor, a radio resource control (RRC) reconfiguration message received from a first network and corresponding to the first SIM; decoding, at the baseband processor, a communication received from a second network and corresponding to the second SIM while the baseband processor is processing the received RRC reconfiguration message; determining that the communication received from the second network comprises a higher priority than the RRC reconfiguration procedure of the first SIM; in response to determining that the communication received from the second network comprises a higher priority, processing a context of the RRC reconfiguration procedure of the first SIM; based on processing the context: completing the RRC reconfiguration corresponding to the first SIM when the context corresponds to a handover procedure, completing the RRC reconfiguration including informing the first network of coordinated leaving; and aborting the RRC reconfiguration corresponding to the first SIM when the context corresponds to anything other than a handover procedure, aborting the RRC reconfiguration including informing the first network of coordinated leaving; transitioning the first SIM to an idle mode; and encoding, at the baseband processor, an RRC request corresponding to the second SIM for transmission to the second network.
 19. The method of claim 18, further comprising: decoding, at the baseband processor, a timer from the first network for the first SIM, the timer being included within the decoded RRC reconfiguration message, the message being generated and transmitted by the first network upon identifying the LTE has multiple SIMs during a capability exchange upon connection of the first SIM to the first network, the timer including a set amount of time; and transitioning the first SIM to an idle mode when the set amount of time has passed after informing the first network of coordinated leaving.
 20. The method of claim 19, further comprising receiving a release locally from the first network corresponding to the first SIM. 